Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


nry last won the day on February 24 2016

nry had the most liked content!

Community Reputation

4 Neutral

About nry

  • Rank
    Advanced Member
  1. I've only ever followed the guides on here, so we have one group for Win7, one for the Server OS, one for Office, one for SQL Server... Seems to work fine here.
  2. We had that too...after I also then upgraded to SCCM 2012 v1511 it magically fixed itself...
  3. Even on 1511 I am still getting this error...completely baffled! The network itself is file again, clients deploying OK with applications being deployed etc. but the SCCM Server continues with this error...
  4. No just one domain, one SCCM server, it is now installing OK on clients again which is a good start after the 1511 update WSUS sync now seems broken too...the joys Chris
  5. OK, upgraded SCCM to 1511 and still the same error except the client version is reporting the correct newer version, MP in the error is still being reported as the old version above...
  6. The MP reports as the correct version the client is looking for, so why is the client seeing the wrong version?
  7. Did you get this resolved? I'm having a similar issue myself.
  8. Any ideas on my next step anyone? I'm going to try CU3 initially!
  9. Hi all, We've been running in to a few weird issues recently, but I'm not 100% sure where they have come from. We updated SCCM 2012 to SCCM 2012 R2 SP1 about 2 months ago, and according to 'About' for SCCM this worked fine. This week, seemingly randomly as I have not changed anything on the SCCM Server (2008 R2), clients have stopped installing any software. We can still deploy the OS as before through PXE/MDT, Windows 7 Enterprise x64, but no software is hitting these machines or existing ones. The SCCM Client installs but then goes into a loop trying again every few hours. On a handful of machines I took some advice from other websites which seemed to fix it, but now nothing is working - the CCMCACHE folder stays empty, SCCM Console can see the new PC's but they are not listed as having the client. I did a little digging on the server and noticed it was doing the same thing with the SCCM Client trying to upgrade I presume from the SP1 update. It was failing so I did a manual uninstall, then used the Console to push out the Client and monitored the install logs. I see this error: The client version 5.00.8239.1000 does not match the mp version 5.00.7804.1000 The MP seems to be stuck on the pre-SP1 version - I removed this role and re-added it but the same error is showing. Can anyone advise on steps to try and troubleshoot and hopefully resolve this? We have a good number of new computers to roll out and we're rather stuck I debated going to the latest CU patch, but unsure if this is advisable or not and even whether this is the best initial approach? Thanks for any help, Chris
  10. I have the deployment working fine following this, however the OS installs to 'D' as opposed to 'C', any way I can change that? Chris
  11. To confirm it is all back behaving as expected! Win7 x64 deployments working fine, Windows 10 deployment also working but I've not set these up within MDT further yet, just the base no-touch install.
  12. I was barking up the wrong tree..no idea why but my previously working driver package for onboard LAN was not being detected during OSD - I sorted a new driver and voila, all fine
  13. Hi all, I have got SCCM 2012 SP2 installed OK, ADK 10 (the original version) installed and MDT 2013 Update 1 all running, PXE boot is working as expected however with the new boot images, I am unable to insert the network card driver that we used previously. Our laptops need the driver available otherwise they boot and install with no network connection therefore no domain join etc. I am deploying Windows 7 Enterprise x64 SP1. Trying to add the original driver that worked on the previous boot images fails, the error suggests an unsigned driver but it is listed as Microsoft signed - is it perhaps more that the new boot images are Windows 10 PE based and need a different driver, or should I still be able to use the old one? There is no Windows 10 driver but I would presume this is not the right one - or should I still be using the old boot image for this deployment? Thanks for any reply, Chris
  14. I'm not sure it matters...I generally test the upgrade then I don't need to worry about the uninstallation part...maybe I'm lazy
  • Create New...