Jump to content


CurtMGray

Applications take forever to install during OSD everything else seems fine though

Recommended Posts

I've got everything working, applications are installing, drivers are updating, client works fine, but the entire process takes FAR too long to complete. I think I've narrowed it down to the point where applications are being installed to the image. Stuff like 7zip and adobe reader are taking upwards of 20 minutes to install each, other applications are behaving similarly.

 

It looks like the drive is really active for awhile, and then just idles along until it finally decides to hit the next installer or step. Digging through smsts.log doesn't seem to show me anything worthwhile, and I'm a little curious if the log is showing everything it should be.

 

Any ideas on what I can look at to get started clearing this up?

Share this post


Link to post
Share on other sites

Really, any ideas here are better than none. Here's some more information about my setup...

  • We are running SCCM 2012, we are not running SP1 at this time, it will be rolled out later this month or so.
  • It seems like the applications are downloading from the server pretty quick, I don't get the impression that the network is the hold up, though I could be wrong.
  • All the same, the content is loaded only on the local distro point, so that should keep weird network traffic to a minimum
  • All of the applications are being installed via .msi packages, and they are successfully installing by the time the whole thing ends.
  • The original wim is pulled directly from MS's ISO for Win 7, I wanted a super clean image to work with and this seemed like a good starting point
  • I've also set up driver installs from Dell's cab files, these seem to be going along pretty well, though that part may be running slow too, it doesn't feel as slow as the appliactions, but I'm not sure how to verify that part

Here are the log files I scavenged at the end of the application install step...

 

dism.log

smsts-20130617-093722.log

smsts.log

wpeinit.log

 

Edit: added more information to the last bullet point.

Share this post


Link to post
Share on other sites

Not sure if it will help, but I came accross a problem where, say I had multiple versions of a program (flash for example), I had one for IE, one for Firefox, and also older versions, all in the same folder.

 

When I told SCCM to install it, it actually ended up copying accross over 200mb of files each time it was installed on a PC. Sometimes it would even fail.

I then moved the single one I wanted in to its own folder within the current location of files, and called it something like Flash_SCCM, copied the file I wanted, updated the advert to show the new location of the file, and it seemed to fix that problem for me.

 

If you check software center on a desktop, it will show you how big it is for each program, I find Adobe Reader to show around 45mb, as an example. Hope this might help a little?

 

Phil

Share this post


Link to post
Share on other sites

we are not running SP1 at this time, it will be rolled out later this month or so

 

 

 

Well, that's exactly what's causing your problem. The behavior of slow apps got fixed with SP1. If you check your smsts.log during the app install, you will see, that the whole task sequnce is getting compiled again before every single application.

So install the SP1 and you will be good.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.