- Sysprep halts at computer name
- Posted by Mikeee on January 20th, 2006
I've been involved in system preparation for quite some time now.
I've been using sysprep on Win 2000, Win XP and some with Win 2003.
Up until now we've always wanted sysprep mini setup to stop and wait for us
to input the computer name.
We've been tasked to upgrade over 1000 computers from Win 2000 to Win XP.
So we've been looking real hard at doing some of them using USMT, and some of
them using Ghost Solution Suite's -> move the user function.
The problem that I've run into with the move the user process is that
sysprep minisetup halts at the computer name, which causes the whole process
to fail. Which is a show stopper in accomplishing this remotely
I've tried several different things with no success.
I added the "computername" into sysprep. I tried ComputerName=* and ="*"
in the [User Data] field but neither seems to work.
I also tried adding UNATTENDEDMODE=FullUnattended in the [Unattended] field.
Still no luck.
I'm at a loss on this one. Anyone have any ideas ?? I have a real short
fuse on this so any help will be appreciated!
- Posted by Michael Niehaus [MS] on January 20th, 2006
This should work fine:
[UserData]
ComputerName=*
What switches did you specify when running Sysprep for capturing your image?
It is really running mini-setup?
-Michael Niehaus
Systems Design Engineer
mniehaus@microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mikeee" <Mikeee@discussions.microsoft.com> wrote in message
news:9349F0DA-30CC-49D6-8818-ED2EE42A5B56@microsoft.com...
- Posted by Mikeee on January 20th, 2006
Thanks for your quick response. Unfortunely, I've tried this several times
and it still halts at the computer name. This is really driving me nuts
trying to resolve it.. Especially since the answer should be so easy to
resolve. But isn't !!
Looking for more idea's
Thanks
Mikeee
++++++++++++++++++++++++++++++++++++++
"Michael Niehaus [MS]" wrote:
- Posted by madsdad on January 20th, 2006
Michael the command that is being run for sysprep is
#-198 Command line processed: C:\Sysprep\sysprep.exe -pnp -quiet -mini
-reseal -noreboot
Mark
I hope this helps
"Michael Niehaus [MS]" wrote:
- Posted by Michael Niehaus [MS] on January 20th, 2006
That seems reasonable (although the "-pnp" isn't recommended and probably
isn't needed). Can you take out the "-quiet" switch to make sure that
Sysprep is successfully completing? Can you provide your complete
Sysprep.inf?
-Michael Niehaus
Systems Design Engineer
mniehaus@microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights.
"madsdad" <madsdad@discussions.microsoft.com> wrote in message
news:CAE34B26-410E-4BF2-8CFE-95F25280F9D9@microsoft.com...
- Posted by Mikeee on January 21st, 2006
Sure.
; SysPrep.inf for Windows XP-2003
;; 23 Nov 05 - Update for New Gold Master 23 Nov 05
;;; 7 Dec 05 - Elim Mass storage segment per UIU
;;; 18 Jan 06 - Modified so it will not stop at computer Name - will use
autoname = for Move the User and training room.
[Display]
BitsPerPel=32
Xresolution=1024
Yresolution=768
Vrefresh=75
AutoConfirm=1
[GuiUnattended]
AutoLogon=Yes
AutoLogonCount=1
OEMSkipRegional=YES
TimeZone=10
OemSkipWelcome=1
OEMDuplicatorString = "Win XP w/SP2 + Office 2003SP2 - UIU - Full package -
18 Jan 06"
[Identification]
JoinWorkgroup=xxxxx
[Networking]
InstallDefaultComponents=Yes
[Shell]
DefaultStartPanelOff = Yes
DefaultThemesOff = Yes
[Unattended]
UNATTENDEDMODE=FullUnattended ;Tells sysprep not to stop for anything
including errors
OemSkipEula=Yes
KeepPageFile=0
UpdateInstalledDrivers=yes
DriverSigningPolicy=Ignore
TargetPath=\WINDOWS
[UserData]
ComputerName=*
ProductKey="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"
FullName="xxxxx"
OrgName="xxxxx"
[sysprepcleanup]
Service=atapi
Service=pciide
Service=intelide
Service=aliide
Service=viaide
------------------------------
"Michael Niehaus [MS]" wrote:
- Posted by Adam Leinss on January 22nd, 2006
=?Utf-8?B?TWlrZWVl?= <Mikeee@discussions.microsoft.com> wrote in
news:E4A94654-5AB8-48B7-B511-D510844F6E1F@microsoft.com:
You probably won't believe this, but I think your problem is the
comment at the end.
I use to put comments at the end of commands
myself and then wondered why sysprep was ignoring my commands. Try
moving the comment above the command line like this:
[Unattended]
;Tells sysprep not to stop for user input
UNATTENDEDMODE=FullUnattended
Adam
--
Visit my PC Tech blog at www.leinss.com/blog