Jump to content


pembertj

Established Members
  • Posts

    81
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by pembertj

  1. That's what I figured but thought I would double check that there wasn't some hack so that you could test out a restore on a test domain. Thanks for the info ~Tom
  2. Playing with the site restore feature in SCCM 2012. I have a separate test domain where I have restored my site backup. The problem that I am running into is that the users who are granted console access do not exist in the test domain. Is there any method to manually add a new user access directly in the SCCM database or some other method that I could use to add a new user to have console access? Thanks ~Tom
  3. In my case it looks like removing Flash NPAPI 17 from the base image will make this error not happen during the OSD of the base capture. ~Tom
  4. For anyone who may run across this post in the future - at least in my case it seems to be related to applications that are installed in the base capture image. I saw at least one forum post on technet that had a similar issue. I removed all application installs and re-captured the base - it then installs fine and installs drivers fine. I am going to narrow it down today and find which app was causing the problem... Recently added apps in my case: Flash ActiveX 17 Flash NPAPI 17 Java 1.7.67 x86 Adobe Reader DC ~Tom
  5. getting this exact same error/problem. Any one else run into this? It has worked fine in the past and just started having problems recently. I have re-built by boot image, re-imported drivers,and re-captured my base image and am still running into this error WinPE phase goes fine. TS stops on the right model and downloads the drivers (WMI Query correct) - but then doesn't seem to apply them. When it gets into the windows phase there are no NIC drivers and TS fails... Thanks
  6. I am running into a seemingly strange problem - maybe I just don't quite understand how supersedence is supposed to work - here is the scenario I am running into: 1. App v1 - Deployed to Device Collections as Required and Deployed to user collection (app catalog) as available 2. App v1 - All deployments now pulled 3. App v2 - App v2 setup to supersede v1 in the properties of the application. All deployments of v1 are now replaced with v2 of the application. Users who fall into the user collection are having v1 automatically uninstalled from their machine and v2 is installing - even though the User Collection deployment is set to Available and not Required. Also the checkbox that is listed when you deploy the application to the User collection "Automatically upgrade any superseded verions of this application" doesn't really make sense to me - isn't this what is done in the properties of the application? Currently this box is uncheck on the deployment. Thanks for your time ~pembertj
×
×
  • 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.