Actually you do not have to enter install mode for a Terminal Server for computer based Windows Installer installations (it is handled automatically by Windows Installer), and I suppose this is computer based installations since Steve mention that the problem is during boot. Installing using GPSI to deploy per-computer assigned software is fully supported and I would say that this problem really is connected to the NICs and a timing problem with the drivers and foreground Group Policy processing. Also I would say that using automated installations and policies is a great for Terminal Server as long as the deployment is properly tested first, something that obviously is true even for deployments to other systems as well :). Group Policy is designed to make it possible to set up the configuration once and then have these settings apply without risk of human errors in the processes, and this is equally true for Terminal Servers as for other systems. Using GPSI and other GP settings makes installation of new servers an pretty easy task instead of putting the administrator in a situation where he or she need to make sure that every server is set up the exact way as the previous servers. This is of course also a great thing if the server need to be replaced. And to be honest, I personally believe that the product teams in Redmond comes up with great stuff pretty often, but blocking GPSI from doing per computer installations on Terminal Server would not have been a great feature if you ask me ;) Best, Thorbjörn Sjövold Special Operations Software www.specopssoft.com thorbjorn.sjovold a t specopssoft.com Download our free tool for remote Gpupdate with graphical reporting, http://www.specopssoft.com/products/specopsgpupdate/ -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Omar Droubi Sent: den 10 maj 2007 22:09 To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: New Dells Not Installing Software Steve, I wouldn't recommend doing any automatic install of software on terminal servers- especially if the terminal server stability is important to your organization. Terminal servers requires that the installation mode is changed from install to execute before you install any software on those systems- that will happen automatically if you initiate the software installation from the add/remove programs applet or if you go to the cmd prompt and type change user install |execute | query. Maybe the developers @ Microsoft finally thought of something worthwhile and this is getting blocked because it is a terminal server. My 2 cents. Omar -----Original Message----- From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Evans Sent: Thursday, May 10, 2007 9:49 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] New Dells Not Installing Software I'm trying to push software to our terminal servers via GPO. Our latest batch of Dell's are failing at this. At bottom we get 1053 errors from Userenv. Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted. The computer and user policies are taking effect though, and refresh properly after boot-up and/or logon. It's only during the boot up process that we're unable to access GPO's. We've run into this before but updating the NIC drivers fixed it. I've done the same on these (Dell 2950's Broadcomm NetXtreme II) but no improved results. Any ideas on what could be going on? Steve Evans *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************ *********************** You can unsubscribe from gptalk by sending email to gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by logging into the freelists.org Web interface. Archives for the list are available at //www.freelists.org/archives/gptalk/ ************************