Link to home
Start Free TrialLog in
Avatar of Thor2923
Thor2923Flag for United States of America

asked on

I am trying to deploy software to a workstation using SCCM 2012r2...How so I add a device to a Device Collections?

We have a Windows 2012 domain and I have started to work with SCCM. I am getting familiar with the Configuration Manager and have set up a deployment package. I go to my package and select DEPLOY. The next screen prompts me to select a COLLECTION. I choose Browse and see several Device Collections are already set up including a TEST. I cannot seem to figure out how to get the workstation I need to deploy software to or a group of workstations into any of the DEVICE COLLECTIONS. Is there something I need to do in Active Directory? If I got to Assets and Compliances > Overview > Devices, I can see the device I need but do not see how to deploy directly to it or move it over to a Device Collections. If I navigate over to Assets and Compliances > Overview > Device Collections, I see an empty TEST Collection I could use but have no idea how to add workstations or devices to it. All advice welcome....thanks
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

In the SCCM console, in assets, devices, right click on a decide. There is an option in the right click menu (and also in the ribbon above) to add the device to an existing collection or create a new one.
Avatar of Thor2923

ASKER

I do all that and my Device Collection still shows 0...is there something I need to do first? See the picture I uploaded
It'll refresh and update the count..
ok I think I have it....I did not realize it took a while to update
ok, it was a frustrating evening. I cannot seem to get anything to push out. Not sure what I am missing. First I tried to create a package with help from the vendor and went through the deploy procedure taking mostly defaults. I go to Monitoring > Overview > Deployments and it is still sitting at 0.0 compliance a day later. I tried creating an application using just one of the MSI files in the package, went through deployment, pointed it to the correct Device Collector, that has my one workstation, and nothing...hours later still at 0.0 compliance. Now, If I try to restart the deployment procedure it tells me that the "application has already been deployed to my collection" so I am kind of stuck and must be missing something on how to start it. NEXT, I downloaded a MSI for JZIP. I just want to make sure I understand the procedure. I created an application using the MSI, selected DEPLOYMENT, pointed to my Device Collection, with my one workstation, and tried to begin deployment. I am still sitting on 0.0 compliance in the monitoring section. Nothing seems to actually start the push. What am I missing?
Could be a lot of things. A common culprit is maintenance windows. The SCCM  client won't kick off an  install outside of the  maintenance window ( which is  default to late overnight) unless a deadline has passed. So your  application today usually  wouldn't install until tonight.

However this is well beyond the  scope of your original question. If the original  issue has been solved, you should close this and open new questions as needed with appropriate details so more experts can participate. Many experts will ignore this question because they'll see what you asked , see that I  accurately answered, and decide the  rest is tl;dr.
ASKER CERTIFIED SOLUTION
Avatar of Mike Taylor
Mike Taylor
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
In addition to the information provided above, I would add that SCCM is not a good idea to dive in headfirst with no knowledge.  It is a minefield of logic-defying problems and headaches if you don't have a grasp of it's fundamentals.

I would suggest buying and reading "Configuration Manager Unleashed" or something similar.  These are books written by ConfigMgr MVPs and are immensely helpful to new and experienced users alike.
Hi,

I agree with Dean - SCCM is not for
a) people in a hurry
b) people who want quick results without experience
c) a quick fix for "deploying patches to every PC"

There's a trend there. It takes time to learn, longer to master and patience to use. You need to channel your inner Zen. Rushing will not work and likely end up in tears.

I recommend Kent Agerlund's book for a thorough walkthrough of the various common tasks. It has step-by-step exercises. For the hardcore theory, get the Unleashed book.

Finally, if you are learning, then now would be a great time to learn some PowerShell too. It is quicker than clicking, but do NOT do it in production. Build your own lab on a PC. You just needs lots of big, fast storage. Kent's book covers that too!

Mike
I got it worked out....a lot of it was just patience