April 01, 1999 03:01 PM

Microsoft's New SysPrep Tool

Rating: (0)
Windows IT Pro
InstantDoc ID #5047
SUPPORT FOR CLONED SYSTEMS
BUILDING LARGE NETWORKS takes time. The more systems you need to build, the longer the rollout will take. Suppose you have to build 500 Windows NT 4.0 workstations from scratch. If each system build takes an hour, this 500-hour rollout will take one administrator 12 forty-hour weeks and 1 day to complete, or four administrators 3 weeks and 5 hours to complete—assuming each workstation takes only 1 hour to build. With applications added to the OS installation, the build-time increases exponentially, right with the total cost of owning those workstations.

Dis...

...This article is for paid Professional Members only.

Already a Professional Member? Please log in now:

NOT A PROFESSIONAL MEMBER? YOU CHOOSE:

Professional Membership

Monthly

Annual

VIP Membership

Monthly

Annual

Add a Comment

I dont seem to have the service SERVER to start with, what is up with that? What am I missing?

Anonymous User 5/2/2005 2:36:35 PM


Great thread and thanks wbeck.
I figured out that the reason the server service wasn't running on my computer - and therefore the reason sysprep wouldn't run, is because I had removed the Microsoft File and Print Sharing service in the properties for my local area connection.
I guess that step needs to wait until after ghosting.

Anonymous User 3/30/2005 6:41:59 AM


Ran sysprep at command line after I got the message "Your grace period limit has been reached and will not be reset."

Used -activated and -reseal parameters. Ghosted image to server. Dropped this new image to two other machines. Restarted those machines. Never prompted for XP key(s).

What do I need to do on the command line to make the systems generate that question?

Anonymous User 3/28/2005 11:24:36 AM


Has anyone encountered Sysprep 2.0 taking a long time in doing it's "thing" so to speak on first run? When I run sysprep on a machine for the very first time it takes forever before it shuts down. I get a window that says "Sysprep is working" and I hear a lot of work going on but it takes about one hour before it shuts down. On second run, sysprep runs as expected and runs just fine--takes less than 30 (even less) seconds before it shuts down. Here are some specs:

OS: WXP SP2 w/latest updates
System: Optiplex Gx110
RAM: 256 MB (at first I thought it was a ram issue)
Sysprep file location: C:\\Sysprep
Use mini-setup is selected (I also thought this was related because I hadn't selected it at first). I'm at a loss and I haven't found anything online. Any ideas? Thanks!

Anonymous User 3/25/2005 8:01:54 AM


blah

Anonymous User 2/28/2005 10:24:08 PM


Does Computer settings software installation,Assigned software installation in AD base its succesful completion of software installation on the SID? After sysprep, moving the same machine back into the same OU re-installs the software.

Anonymous User 2/8/2005 1:33:52 PM


Phil,

Thanks for the tip--I had been wracking my brain, and the server service was the problem.

Bless you!

--Mike

Anonymous User 2/7/2005 4:59:02 PM


Nice work on figuring out that the server serice must be installed to run sysprep. What a pain in the ass. Nice of Microsoft to fail to document this....

Cheers
Phil

Anonymous User 1/14/2005 9:24:19 AM


thanks tons, wbeck!

Anonymous User 12/20/2004 4:24:24 PM


I have the same problem with sysprep, there has to be something I can do instead of creating a CD.

Anonymous User 12/16/2004 7:08:13 AM


You must log on before posting a comment.

Are you a new visitor? Register Here
GOOGLE LINKS
SPONSORED LINKS
FEATURED LINKS