Posts Topics Forums Images
Search videos from message boards Videos Search messages from microblogs Microblogs Search messages from imdb.com Imdb Search messages from yuku.com Yuku Search messages from lefora.com (free forums) Lefora
My account: Login | Sign Up
Loading... 

Thread: Total Time for OSD

Started 1 month, 2 weeks ago by waynegro
Hello everyone, I am curious to see how long your OS deployments are taking. Here I am doing a bare metal install of Windows 7 (from installation source), Office 2007, and several HP driver packages that won't import into the driver category. Right now this takes 2 1/2 hours to deploy. This is not an acceptable time. What, if anything, can I do to get this into the 1/2 hour to 45 minute range?...
Site: Microsoft TechNet Forums  Microsoft TechNet Forums - site profile
Forum: Configuration Manager Operating System Deployment  Configuration Manager Operating System Deployment - forum profile
Total authors: 7 authors
Total thread posts: 24 posts
Thread activity: no new posts during last week
Domain info for: microsoft.com

Other posts in this thread:

mclanem replied 1 month, 2 weeks ago
Definatly capture at least office in an image and deploy using that.  My current Task Sequence including USMT with 40 Gig on a users desktop took about 40 minutes the other day.  Wrapping as much as you can into an image will really increase the speed of your deployment.  I also find that the driver installations work better when you use an image. Matt

Jason Sandys replied 1 month, 2 weeks ago
Images are definitely the preferred method for mass deployment. Installing from source using a build & capture task sequence to ultimately capture the image is the best thing to do and then use that image for mass-deployment.

Kenny Buntinx replied 1 month, 2 weeks ago
Hi there , An image is not always needed to get a fast deployment . ( Depending on the size of your apps ) Did you select in your program : Run from Distribution point instead of Download from the Distribution point änd Install . This makes a huge difference in time ! Hope it helps Kenny

Eric Zhang - MSFT replied 1 month, 2 weeks ago
Hi, Sometimes the formatting disk section would go on for greater than 30 minutes.You can choose to use "quick format" In the Task Sequence, Install Operating System -> Partition Disk -> Volume -> Edit Primary -> There is a check box for ‘Quick Format’. Also, If you are using SCCM 2007 SP1, there is a hotfix, KB955955 which you should apply, as it removes a delay between tasks, which, for ...

Kenny Buntinx replied 1 month, 2 weeks ago
Erik , He is already on SCCM SP2 as he is busy deploying Windows 7 clients. But you are right , formatting should be put to  ‘Quick Format’ as a normall format takes way to long. Kenny

Kenny Buntinx replied 1 month, 1 week ago
Hi , It is very normal that symantec is beating that , because it is a sector based imageing tool . SCCM is using file based imaging .2 different worlds Also you are comparing apples with cherries ... XP + office is about 2 gig image , while win7 with office is a 6 gig image !! Double the size , double the time . If you really want to ty down the time for staging , you make an offline Task ...

waynegro replied 1 month, 1 week ago
I don't necessarily need something that uses the same technology, but I do need similar performance. I don't mean to outright compare the two products, that's just what we have now (it has worked very well for us) and we're looking for something comparable to upgrade to since support for that product has been dropped. I am trying the offline media option now. Hopefully this will fit on a 4 GB ...

waynegro replied 1 month, 1 week ago
Formatting has always been set to quick format; one of the first things I found and it does take a ton of time out of the process.  I created a task sequence to deploy a bare metal install with Office 2007 and take an image of it with success. I am now in the process of deploying that image to a laptop. It has been working for just over 1.25 hrs now on a 100Mb backbone. This is better than the ...

Jason Sandys replied 1 month, 1 week ago
WIMs created by imagex are compressed by default. How big is your image?

waynegro replied 1 month, 1 week ago
Pushing 3 GB as a bare install with office 2007 only (and that Office is modded to only install Outlook, Excel, PP, and Word). That is the size of the newly created WIM file.

 

Top contributing authors

Name
Posts
waynegro
11
user's latest post:
Total Time for OSD
Published (2009-11-20 18:02:00)
Well, I have now tested this deployment over a GB backbone with much faster results. I knew there would be some increase in speed but did not know how much it would actually be. Without making the registry changes or block size changes I deployed an image containing only a base OS with Office 2007. The time from the first boot to login was 20 minutes. This is workable for us now. Consider this solved. Thank you all for your help!
Kenny Buntinx
5
user's latest post:
Total Time for OSD
Published (2009-11-18 06:38:00)
Hi , I wouldn't play with the block size unless you use jumbo frames on your network switches or computers ... You just need to live with the fact your image has been tripled in size and that it triples the deployment time as well . Regards , Kenny
Jason Sandys
3
user's latest post:
Total Time for OSD
Published (2009-11-12 18:21:00)
What Kenny is comparing using the "apples to oranges" phrase is not Microsoft to Symantec, rather he is comparing the size of XP image to the size of the Win7 image. Transfering 3GB across a network, especially a slow 100MB network, takes time no matter what deployment tool you are using. Win7 images are just bigger because Win7 is bigger, there is no getting around this one and you must set your expectations based on this...
mniccum
2
user's latest post:
Total Time for OSD
Published (2009-11-13 18:06:00)
Might want to check into this also.  It will shave off a few minutes: http://support.microsoft.com/kb/968718   Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\PXE Name: RamDiskTFTPBlockSize TYPE: REG_DWORD Value: <the expected block size> Haven't tested it with Sp2 and be careful setting it to high if you have older machines. Mike
Eric Zhang - MSFT
1
user's latest post:
Total Time for OSD
Published (2009-11-12 06:47:00)
Hi, Sometimes the formatting disk section would go on for greater than 30 minutes.You can choose to use "quick format" In the Task Sequence, Install Operating System -> Partition Disk -> Volume -> Edit Primary -> There is a check box for ‘Quick Format’. Also, If you are using SCCM 2007 SP1, there is a hotfix, KB955955 which you should apply, as it removes a delay between tasks, which, for long...
mclanem
1
user's latest post:
Total Time for OSD
Published (2009-11-11 20:10:00)
Definatly capture at least office in an image and deploy using that.  My current Task Sequence including USMT with 40 Gig on a users desktop took about 40 minutes the other day.  Wrapping as much as you can into an image will really increase the speed of your deployment.  I also find that the driver installations work better when you use an image. Matt
TKC Global
1
user's latest post:
Total Time for OSD
Published (2009-11-18 16:44:00)
Here is a reference for Windows 2008 WDS: http://technet.microsoft.com/en-us/library/cc731245(WS.10).aspx "We recommend that you go up in multiples (4096, 8192, 16384) and you should not set a value higher than 16384."

Related threads on "Microsoft TechNet Forums":

Related threads on other sites:

Thread profile page for "Total Time for OSD" on http://social.technet.microsoft.com. This report page is a snippet summary view from a single thread "Total Time for OSD", located on the Message Board at http://social.technet.microsoft.com. This thread profile page shows the thread statistics for: Total Authors, Total Thread Posts, and Thread Activity

This page was found by:   total percentage interrupt time is too high  RamDiskTFTPBlockSize  RamDiskTFTPBlockSize sccm