 |
 |
Testing... |
 |
|
|
Main Menu |
|
|
|
Topics |
|
|
|
Voice Over IP |
|
|
|
Last 10 Articles... |
|
|
|
Search this site |
|
|
| |
|
This blog is no longer updated.
Since I own the domain name for a couple more years, and the hosting was paid-in-advance, it's still here. But I've moved on to Hawaii, and no longer have the need to publish all the sorts of neat stuff that made up the contents of this website.
If you've linked to me, you are invited to unlink, as your readers will no longer be presented with new content. Thanks, Steve
Installing Windows 2003 Service Pack 1 via Terminal Services
Tuesday, July 05, 2005 : Stephen D. Carroll, rokus.net
|
|
I've had the "opportunity" to install Win2K3 SP1 via TermSvc quite a few times this week. There's nothing more exciting than rebooting a server remotely and seeing finally respond to a ping -t.
Until you attempt to remote desktop into the box and it won't respond. It's up - services are running, you can connect to the management console, and you can read her event logs. It really sucks when the boxes are an hour or four away. Had to login to console for the local servers and re-enable remote desktop. Wasn't particularly looking forward to another road trip.
Killed me all week - SP1 turns off the remote desktop. By design, by mistake, in general, or just in my particular setup, every single time.
You know you get one of those Homer J. Simpson "DOH!" moments? Yeah, I had mine.
Under HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server, change fDenyTSConnection (REG_DWORD) the value data from 1 (Remote Desktop disabled) to 0 (Remote Desktop enabled).
DOH!!
|
|
Permalink | Mail this...
|
|
| Installing Windows 2003 Service Pack 1 via Terminal Services | Login/Create an account | 0 Comments |
|
| | Comments are owned by the poster. We aren't responsible for their content. |
| |
|
|
|
