Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About PR.

  • Rank
  1. Patience? Check the client settings on device affinity to make sure the numbers apply to how long your users are logged in. On our system it took a good few weeks before SCCM started building up the information. Have you checked that you can manually assign a primary device?
  2. I did have problems with it initially, I'm not sure what the problem was but I removed the Reporting Point, updated SQL 2008 R2 to CU6, cleared out the old ReportingServer databases and reinstalled and configured the Reporting Point and it worked ok. I can create new reports and they run correctly, but the default ones are not present. Thanks
  3. I've gone and added the Reporting Services Role and managed to create a report myself. However none of the default reports are listed. Is there some way of getting them recreated? Thanks
  4. Possibly WinPE doesn't have the NIC drivers for the system you're attempting to deploy to? If you followed the guides here, press F8 at the failed task sequence window to open the command prompt and type cmtrace then use the log viewer to open the log files (located in <largest fixed partition>\SMSTSLOG), from there it should be clear what's preventing the task sequence running through. If F8 doesn't do anything, on CM2012 you need to go to Software Library > Operating Systems > Boot Images > properties of your images > Customisation tab > tick "Enable command support (testing only) then click ok and rebuild/redeploy the images and try again.
  5. I followed what Desek above said The source wim files are usually in folders within <drive>:\RemoteInstall. My issue wasn't that I couldn't create the image files from CM2012 but that they simply refused to copy to their distribution points. Once I'd forced them the first time (following Deseks's instructions) the PXE service picked them up straight away. I've had to update them several times since with NIC drivers and they have happily deployed themselves automatically without having to repeat the manual process
  6. This was the same error I was getting but not sure everyone is having the exact same issue... Have you tried this to manually force the boot image to deploy - http://www.windows-noob.com/forums/index.php?/topic/4716-fail-to-test-the-pxe-on-sccm2012/#entry19437 I was getting absolutely nowhere until I did this now it works as expected.
  7. Yup, I created an "Endpoint Deployment" collection then added one of our offices collections to see how it handled uninstalling the existing clients. Once I was happy I modified the Endpoint Deployment to include all the other office collections I have and it deployed to the remaining clients over a couple of days. Once they are installed they automatically pick up the Antimalware policy they are assigned to and configure themselves, you can check from Assets and Compliance > Devices > -device- > Endpoint Protection tab, it should read as managed, and the appropriate policy listed next to it.
  8. //EDIT - Doh, sorry ignore, the half dozen machines I checked don't have primary users, but I've checked others and they do so it does seem to be working after all! Has anyone managed to get this to work automatically? I set it up at the beginning of the month, and configured the client settings using the default values. However nothing was populated in the Primary User for devices. I then reconfigured it to: User device affinity usage threshold (minutes) - 840 User device affinity usage threshold (days) - 10 Automatically configured user device affinity from usage data - True Allow user to define their primary devices - True My reading suggested that if a user used a device for at least 14hrs over a 10 day period that would be assigned as a primary device. Three weeks later, still nothing is being recorded, most users work 8am-6pm Monday to Friday so the rules above should have triggered the system. I even have users who stay logged in 24/7 and they aren't recorded either. I did also read that I would need to set auditing of logon/logoff events on client machines, but again this has made no difference. Anyone have any ideas? Thanks
  9. I would like to add that since manually copying the images over, I have rebooted the server and updated the boot images several times and had no further issue. It was just that initial deployment that refused to work.
  10. I have never really used SUP as I find it much more labour intensive compared to WSUS but I would guess that you can't use a remote WSUS server. CM2012 only uses components of WSUS to deploy updates so they would need to be installed locally. If you're currently using WSUS on another server, you would first install WSUS on the CM2012 server (cancelling the configuration) turn off WSUS on the remote server and cancel any GPO WSUS assignments. Then setup CM2012 to install the updates via the CM2012 client via the very useful guides on this forum!
  11. I did this without any major problems. My CM2007 was essentially broken so I set up a GPO object to switch the site code to the new CM2012 server and enabled push install to all client to allow them to auto update as they switched over to the new site. Only issue I had was a couple of machines are still running XP SP2 which CM2012 doesn't support.
  12. Have you configured the Client Settings to deploy the client? Personally I configured a custom client device setting just for Endpoint (Administration > Client Settings > Create Custom Client Device Settings + tick Endpoint Protection) as I wanted to regulate the deployment. You can then right click on the new settings and deploy them to a collection. Once I did that the deployment kicked off over a few days.
  13. Yer, I'd like to know to, I've set up a load of packages as they were in SCCM2007 but it seems to offer software via the Application Catalog and Software Center you need to use "Applications" instead
  14. Just registered to say thanks to desek! Been having this problem for a week, tried all different things, but couldn't get PXE to boot. Manually copying the images over and it started working straight away. Thanks again!
  • Create New...