Search the Community
Showing results for tags 'automatic'.
Hi, From january 2015 we are getting new laptops. Now I'm looking for a easy way to transfer all users to the new laptops. We use SCCM2012R2. We will be using Windows 8.1. Images are ready, Tasksequences are made and working but here is what I want. We roll out a standard image with some additional software (postinstallation in Tasksequence) like Office2013 and some other generic software. Most of our users have additional software like Adobe CC or Keepass. This software is restricted and users have to a member of a AD security group, so it is available in de Application catalog. For the new laptops I like to automate this process so we (the ICT department) can deploy the standard image plus the software the user needs. So the user gets a fully installed laptop. We do not need to use USMT I'm looking at UDI but it is not working. I just need a list of applications/packages in my current TSQ. Anyone?
Is it possible to set up auto deployment of the SCCM client to a single collection. Here is my scenario... I have SCCM 2012. We build enough servers on a pretty regular basis so that I've created an OU (and a collection that targets said OU) that they can drop the servers into, and they will get SCEP, Updates, standard software, etc. The only issue is, I have to do a SCCM client push before it will install any of that stuff. Is there a way I can target this Collection (OU) for automatic SCCM client installation without having to use GP (The folks in charge of group policy are different than my group, so I want to keep as much of the process internal as possible). Thanks in advance, Jay
Hi Everyone, I think this has been covered here before http://social.technet.microsoft.com/Forums/en-US/configmanagerapps/thread/3fa79201-1ab4-4636-82fc-6862620998e9/ but I cannot get an auto login for domain users to work, it always prompts for password. I have made sure application website is in trusted sites and security for domain users in IIS is set to read? My site is only using http if that's an issue, not https.