+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 28 of 28
O/S Deployment Thread, Any tips for reducing my image size before cloning? in Technical; Turn off windows restore - that frees up a load...
  1. #16

    SpuffMonkey's Avatar
    Join Date
    Jul 2005
    Posts
    2,259
    Thank Post
    55
    Thanked 283 Times in 189 Posts
    Rep Power
    135
    Turn off windows restore - that frees up a load

  2. #17
    Friez's Avatar
    Join Date
    Dec 2006
    Posts
    839
    Thank Post
    22
    Thanked 22 Times in 21 Posts
    Rep Power
    24
    Quote Originally Posted by srochford View Post
    Different users obviously have different needs but in general the benefit of putting everything in the image (compared to using GPO software installation or similar) is that you multicast the software which is part of the image compared to unicasting that which is put out later.

    If you've got (say) a 2Gb basic image and 5Gb of software and 20 machines in a room then you can either do this as 1 x 7Gb multicast or 1 x 2Gb multicast + 20 x 5Gb unicast which probably takes more time (even if you've got a 10Gbit feed to your local switch that's still only allowing you 500Mbit for each of your 20 clients). The benefit of multicasting is even more dramatic if you can do (say) 50 machines at a time.

    There are benefits, though, of keeping the apps separate. If you want to update an app, it's easy to just add the new one to the group policy; no need to redeploy the whole app.
    Agreed, however, I am skeptical that all machines in his workplace need all software. For instance, we only have cubase installed in our music labs, and only photoshop is available for Art. Maybe he can trim down some image size by moving over some of these into appropriate GPO's?

  3. #18

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    18,157
    Thank Post
    522
    Thanked 2,552 Times in 1,981 Posts
    Blog Entries
    24
    Rep Power
    877
    Quote Originally Posted by sted View Post
    because after the 3rd sysprep you cant
    Huh? You can re-sysprep a machine as many times as you want...

  4. #19


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,815
    Thank Post
    231
    Thanked 888 Times in 763 Posts
    Rep Power
    301
    Quote Originally Posted by localzuk View Post
    Huh? You can re-sysprep a machine as many times as you want...
    i thought after the 3rd attempt it stopped letting you sysprep it anymore so you couldnt get round activation by just sysprepping every 30 days

  5. #20

    localzuk's Avatar
    Join Date
    Dec 2006
    Location
    Minehead
    Posts
    18,157
    Thank Post
    522
    Thanked 2,552 Times in 1,981 Posts
    Blog Entries
    24
    Rep Power
    877
    Quote Originally Posted by sted View Post
    i thought after the 3rd attempt it stopped letting you sysprep it anymore so you couldnt get round activation by just sysprepping every 30 days
    Sysprep is not the same as activation... You can sysprep as many times as you want. You can only activate 3 times.

    From the MS site:

    Sysprep must be used only to configure new installations of Windows. You can run Sysprep as many times as required to build and to configure your installation of Windows. However, you can reset Windows activation only up to three times. You must not use Sysprep to reconfigure an existing installation of Windows that has already been deployed. Use Sysprep only to configure new installations of Windows.
    What is Sysprep?

  6. #21


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,815
    Thank Post
    231
    Thanked 888 Times in 763 Posts
    Rep Power
    301
    fair enough i stand corrected but i still think its worth having a pre sysprepped image around

  7. #22
    jack0w's Avatar
    Join Date
    Jan 2008
    Posts
    123
    Thank Post
    12
    Thanked 4 Times in 4 Posts
    Rep Power
    14
    Quote Originally Posted by sted View Post
    i thought after the 3rd attempt it stopped letting you sysprep it anymore so you couldnt get round activation by just sysprepping every 30 days
    I have to admit I was under the same impression. Is this just a myth?

  8. #23

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    7,019
    Thank Post
    1,365
    Thanked 1,771 Times in 1,193 Posts
    Blog Entries
    22
    Rep Power
    530
    Quote Originally Posted by jack0w View Post
    I have to admit I was under the same impression. Is this just a myth?
    Yes. See localzuk's post above

  9. #24

    Join Date
    Jun 2006
    Location
    Belfast, N\'Ireland
    Posts
    190
    Thank Post
    10
    Thanked 9 Times in 7 Posts
    Rep Power
    19
    I'm not convinced that with XP infinite syspreping is a good idea. I use a default image with the basics that every machine receives windows, drivers, couple of system software bits, current windows updates as of when the image was created and CS3 because deploying it by GPO took 3 times longer than including the same data in the image.

    I update the image roughly twice a year but in the 3 years I've been working here I've had to start from scratch a couple of times with most of the images because they became "broken" with multiple syspreps. Not the same exact problem each time but one image developed an issue that made it impossible to connect to WMI on any machine based on it. Another one developed a logon issue for users which repeatedly prevented roaming profiles applying. I did allot of hunting to find exactly what was wrong with them but in the end I remade the image from a clean XP SP3 disc and everything was great.

  10. #25
    MGSTech's Avatar
    Join Date
    Jul 2007
    Posts
    363
    Thank Post
    13
    Thanked 95 Times in 54 Posts
    Rep Power
    39
    Sysprep is not the same as activation... You can sysprep as many times as you want. You can only activate 3 times
    .


    If you used a VLK copy rather thank trying to activate every build (based on an OEM copy of XP)it would cease to be a problem?

    Volume Licence versions of Xp don't need activation, and can be syspreped as often as you like.

    HOWEVER, as sysprep occasionally stuffs up your build when running, it would suggest it WAS a good idea to keep a pre-sysprep inage unless you wish to risk a weeks work making your master image?

    You can always delete it afterwards?

    Steve

    Imaging systems since NT4!

  11. #26

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    7,019
    Thank Post
    1,365
    Thanked 1,771 Times in 1,193 Posts
    Blog Entries
    22
    Rep Power
    530
    I have got into the habit of always using a pre-sysprep image anyway.

    Basically I have a pre-sysprep image and a post-sysprep image. If I need to update my image, I load up the pre, make the change, update the pre, sysprep and update the post. If that makes sense?!

    I know that you can sysprep as many times as you want but I feel more comfortable starting fresh each time.

  12. #27
    Unvalidated User
    Join Date
    Nov 2007
    Location
    the Pub
    Posts
    255
    Thank Post
    7
    Thanked 11 Times in 10 Posts
    Rep Power
    0
    Volume Licence versions of Xp don't need activation, and can be syspreped as often as you like.
    thats what I do and keep images (ghost or Acronis trueimage) of each mainboard

    Might be better ways, but never had time to look at finding the best

  13. #28

    Join Date
    Sep 2012
    Location
    UK
    Posts
    26
    Thank Post
    4
    Thanked 2 Times in 2 Posts
    Rep Power
    5
    Quote Originally Posted by reggiep View Post
    I'm just wondering if anyone has any routines they carry out pre sys prepping a machine? My images have crept up in size and I really need to clear them up a bit!

    For example couldf i remove the windows updates files?

    I normally clear out:

    Windows Temp
    Temporary Internet Files
    User's temp folder
    Windows Updates from C:\Windows ***NOTE: Do NOT delete the folder C:\windows\$hf_mig$ but you CAN delete any folder starting C:\windows\$NtUninstall***

    (If you do the above, you cannot uninstall any applied updates!)

    net stop wuauserv
    Delete the contents of C:\windows\SoftwareDistribution

    The above should save you anywhere between 2 and 6GB if that helps.

    EDIT:

    Just re-read and didn't realise the OP was from 2009! Also had a chuckle at those of you thinking that 12-28GB is big for an image!

    Current image size with compression: 45GB
    Last edited by JPShields; 4th March 2013 at 11:39 AM.

  14. Thanks to JPShields from:

    zag (4th March 2013)

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Making/Reducing disc space on Squid
    By wellscs in forum *nix
    Replies: 6
    Last Post: 18th May 2009, 12:47 PM
  2. Reducing digital photo file size
    By leco in forum Mac
    Replies: 2
    Last Post: 28th October 2008, 08:58 PM
  3. Random print jobs reducing to 25%
    By Nick_Parker in forum Windows
    Replies: 10
    Last Post: 11th March 2008, 01:42 PM
  4. Projector image size
    By _Bat_ in forum Hardware
    Replies: 8
    Last Post: 26th April 2007, 03:13 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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