Sysprep problems?
Results 1 to 7 of 7

Thread: Sysprep problems?

  1. #1
    Registered User HIESLanMan's Avatar
    Join Date
    Feb 2001
    Location
    Atlanta, GA
    Posts
    154

    Post Sysprep problems?

    I've been having an argument with a cow-worker about our deployment strategy. I've got a perfectly good sysprep image made, which automatically configures the machine to join the domain, generate a random computer name, etc. He insists that sysprep can't be trusted, and that we've got to use Drive Image or Ghost to make a reliable image. He's been around a lot longer than I have, so maybe he knows something about sysprep that I don't. Has anyone had any problems with sysprep in W2K? Were there big problems with MS deployment tools in NT, and that's why he's skeptical?
    a LARTing we will go
    a LARTing we will go
    hi-ho the derrio
    a LARTing we will go

  2. #2
    Registered User
    Join Date
    Nov 2000
    Location
    Tananger, Rogaland, Norway
    Posts
    52

    Question

    Maybe I'm totally wrong about this, but maybe you should use sysprep first, then driveimage.

  3. #3
    Registered User
    Join Date
    May 2001
    Location
    New Orleans
    Posts
    290

    Arrow

    Actually, if you *do* use another disc image program, you're going to have a lot of trouble with hooking these computers up to the network, because they will all have identical SID's. By using sysprep, you can specify the /nosidgen parameter, to prevent this.

  4. #4
    Registered User
    Join Date
    Apr 2001
    Location
    Winnipeg, Manitoba Canada
    Posts
    106

    Post

    Clarification time.

    Use sysprep to roll back the system so that it will create the new SID when imaged to another pc. One sysprep is run, use something like Ghost to create an image file to be deployed. Done. After the image is dumped on a system, on the first boot, it will create a new SID and get itself configured. There is no reason not to use sysprep, and as for not trusting it, I disagree. USE IT!!! It's your frind when you want to make your life easier! <IMG SRC="smilies/biggrin.gif" border="0">

  5. #5
    Junior Member
    Join Date
    May 2001
    Location
    Bellevue
    Posts
    9

    Post

    Captain Kirk is absolutely right! First of all /nosidgen will do exactly that, it will not create a new SID. Also if you decide to go with just Drive image (for some insane reason) you can only use that image on machines that have the same IDE chipsets. Do exactly what Kirk said..FIRST sysprep -pnp and then image! There is NO better way for deployment!!!

  6. #6
    Registered User HIESLanMan's Avatar
    Join Date
    Feb 2001
    Location
    Atlanta, GA
    Posts
    154

    Post

    That's kind of what I thought. We did get around some of the problems mentioned (just for the record) by pulling the drivers for the ide controllers before imaging. DI Pro also has a switch that will change SIDs and machine names as well. We ended up doing it his way, but I agree that sysprep is the better way. I just wasn't sure if there was something he knew that I didn't. I guess not! Thanks everyone.

  7. #7
    Registered User
    Join Date
    Jun 1999
    Location
    Toronto
    Posts
    74

    Post

    Hi, try altiris at altiris.com
    not sure if it helps but i seen the demonstration of it at comdex canada and looks premising

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •