Jump to content

Featured Replies

Posted

I have 50 Optiplex 780's that I'm about to deploy. I have installed Windows 7 Enterprise on one of the machines to create an image that I would use for the rest of the machines. I customized it with all of our software and settings. I sysprep'd the machine using this answer file and this command c:\windows\system32\sysprep\sysprep.exe /generalize /oobe /shutdown /uattend:unattend.xml

 

 

 

 

 

en-us

en-us

en-us

en-us

 

 

 

 

QgBpAHQAJQBMAG8AYwBhAGwAUABhAHMAcwB3AG8AcgBkAA==

false

 

true

1

Administrator

 

 

 

 

 

RABDAE4AUgB1AHMAZQByACMAMQBQAGEAcwBzAHcAbwByAGQA

false

 

Helpdesk

Helpdesk

 

 

 

Eastern Standard Time

false

 

true

Work

1

 

 

 

 

 

no

http://intradcnr

true

 

 

*

Eastern Standard Time

false

true

 

 

 

 

false

 

 

 

 

 

The machine shutdown. I captured the image using Ghost 2003. *I know that best practice is using imagex. I just went with what im familiar with due to being short on time.* After starting the pc back up everything works perfect. I can logoff and logon pretty quick. Once I join the pc to the domain and reboot I can logon just fine. I can logoff fine. I reboot the pc. It comes back up to logon. I logon, now when i logoff it hangs.. I shut the machine off from the power button and bring it back up.. Still hangs when logging off/shutting down/or restarting. I found that the first time that you logon to a profile (when domain connected) it works fine. After a restart it will hang. After leaving it sit for 8 minutes it will log off.. If I log back on it will log back off quickly but once it is restarted it takes forever again to logoff/shutdown or restart.. I tried disjoining it from the domain. It works as it should.

I already have 8 machines I built as fresh installs in the same AD Container and those work fine. So I don't think it has anything to do with group policy.

One thing that I ran into when I was sysprep'ing the machine was it would always error out on the copy profile. I would have to start over again from scratch.. Thats when I found out that there was an issue where if there was a registry entry in HKLM\software\Microsoft\current version\windowsnt\profilelist that was not a valid user account it would have issues.. so i removed the entry for the user that was created when I first started to load the machine. It seemed fine.

I also tried going into msconfig>services>Hide all MS services> Then disable all of the services except for the AV. Still an issue.

We do not use roaming profiles or logoff scripts either

Any ideas??

 

Continue reading...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...