Jump to content


SCCMtryhard

SCCM 2012 R2 issues

Recommended Posts

I have been having a number of different issues with SCCM and if you could answer just one question or all of them it would be appreciated.

 

 

1. When creating a device collection, I have noticed that after a while the devices will just disappear out of the collection even though they still exist on the network and still have the client installed, is this a common occurrence? Is there a way to stop devices from disappearing?

 

2. I have run into an issue multiple times where the client just seems to stop working, I force a reinstall of the client and then not too much longer the packages I have pushed start loading, is this a common problem or is there something that can be done to prevent the client from seemingly stopping to work properly?

 

3. I have run into an install that got stuck at content downloaded(given the wording I assume that means it has finished downloading) as the category and for status type it says In Progress for hours. When you run this msi file manually it finishes in maybe 30 seconds. Is this just because SCCM is waiting to install the package or it's installing it very slowly to prevent a slow down to the computer? Is there a way to force it to go faster or is it likely that something has gone wrong? I guess I will just let it go and see if it finishes by the end of the day or by tomorrow.

 

I can't think of any other questions at the moment but I'm sure I will have more later.

Share this post


Link to post
Share on other sites

Been on R2 since the start of the year, and not ran into any of those issues.

 

Clean install, or upgrade from SP1?

 

Do you mean for SCCM or Server 2012 or do you mean the clients Windows 7? What would it mean if it were an upgrade? Unfortunately I'm not sure for any of them, other people configured the server and the image we are using and SCCM and I am using SCCM to create and deploy packages.

 

As far as the app staying in progress a long time, finally days after I deployed it it said

This installation package is not supported by this processor type. So I figured that the issue was it was a 64 bit package being deployed to a 32 bit machine but it's still very annoying that it took that long to give the error message.

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.