Home > Virtual Desktop Tips > Virtual desktop management tips > Install Windows server from local console, not Remote Desktop
Virtual Desktop Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

VIRTUAL DESKTOP MANAGEMENT TIPS

Install Windows server from local console, not Remote Desktop


Serdar Yegulalp, Contributor
04.19.2006
Rating: -4.00- (out of 5)


Expert advice on Windows-based systems and hardware
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


I recently set up a new test server with Windows Small Business Server 2003 (SBS 2003) and ran into an interesting problem.

When I started the test, I only had one monitor on hand (and no KVM switch), so during the first phase of the install I plugged the monitor directly into the server-to-be and popped in the SBS 2003 CD. Everything was going fine. But once I reached the desktop I jumped the gun. I set up the machine to allow Remote Desktop access, disconnected the monitor so I could use it with my main machine, and continued the rest of the setup process from a Remote Desktop session.

What I thought would make my life easier turned out to be a terrible mistake. I'd forgotten about the setup scripts for Windows SBS 2003, and how SBS requires multiple reboots and reconfiguration of the network settings. Not only does this kick you out of the Remote Desktop session (as a reboot would in any case!), but if you try to log back in, you'll face a situation where you have the local console already running the setup scripts and where no interaction is possible.

If you try to reconnect, you get a Remote Desktop session that launches its own instance of the setup scripts. (In theory, it might be possible to work around this, but it's easier to do things right the fir


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


RELATED CONTENT
Virtual desktop management tips
Choosing a connection broker for your virtual desktop
Choosing the right client computing technology
Configuring Active Directory GPOs in a VDI environment
Four good reasons to deploy virtual desktops now
Presentation virtualization: The low-complexity alternative to VDI
Terminal Services get a makeover in Windows Server 2008 R2
How to install Microsoft VDI and key deployment considerations
Third-party virtual desktop technologies for Microsoft
VMware training software allows quick lab set up
Choosing your desktop virtualization software

Virtual desktop management
Choosing a connection broker for your virtual desktop
Choosing between type 1 and type 2 client virtualization
Choosing the right client computing technology
Does the cloud have anything to do with desktops?
Configuring Active Directory GPOs in a VDI environment
Understanding application virtualization as a software hosting strategy
Techniques for overcoming challenging VDI, WAN connections
Four good reasons to deploy virtual desktops now
VMware training software allows quick lab set up
Microsoft enters the VDI market with Windows Server 2008 R2

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary


st time and not try to contrive a solution to a problem that doesn't need to exist at all.)

As a result of this mess, the setup scripts created a damaged system configuration: The post-install claimed certain files couldn't be copied, and the system log was riddled with error reports. Rather than fight the terrible odds of working my way through such a mess, I reconnected the monitor and reinstalled from bare metal. This time, I waited until all the post-install actions were concluded before trying to use Remote Desktop again. The install concluded perfectly and I haven't had a problem since.

One way to get around this problem is to insure that the Remote Desktop connection you set up forcibly overrides any local console logins. If you create a Remote Desktop Connection (.RDP) file and edit it in a plaintext editor, you can add the line

connect to console:i:1

to insure that the connection in question always connects to the local console. (Be sure not to edit the password section of the file!)

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter. Check it out for the latest advice and musings on the world of Windows network administrators.

More information:

Rate this Tip
To rate tips, you must be a member of SearchVirtualDesktop.com.
Register now to start rating these tips. Log in if you are already a member.




DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2008 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts