Welcome to windows-noob.com!
Logging in will allow you to download scripts used in the guides.
If you came here looking for the Endpoint Manager step-by-step guides then please start here.
Register for free and ask your questions in our forums.
- 0 replies
- 2287 views
- Add Reply
- 2 replies
- 6692 views
- Add Reply
- 0 replies
- 1297 views
- Add Reply
- 3 replies
- 4490 views
- Add Reply
- 0 replies
- 1460 views
- Add Reply
- 3 replies
- 4456 views
- Add Reply
- 2 replies
- 4384 views
- Add Reply
- 2 replies
- 2088 views
- Add Reply
PXE boot fail
By Edvin,
I'm starting to get greyhair after all my tries to fix PXE problem I have. The problem started after I removed SUP and Wsus role from the primarysite to a new site. That made the PXE boot fail for some reason.
I'm running SCCM 1606 with 12 servers that have DP and PXE role. Non of them are working at the moment. The error I get is PXE-E53: No boot filename received
This is what i get in the SMSPXE log
RequestMPKeyInformation: Send() failed. SMSPXE 2017-08-31 15:56:08 3216
WinPE Reboots at "Preparing Network Connections" - SCCM 1706
By tacotime,
A few weeks ago I upgraded SCCM to version 1706. Shortly after, I decided to begin building out our environment for Windows 10 Enterprise 1703 deployment. I upgraded our Microsoft Deployment Toolkit (MDT) version from build 2013 Update 2 to the latest version (build 8443) and Windows Assessment and Deployment Kit (ADK) from Windows 10 1607 to Windows 10 1703 in preparation. I added a new operating system image and boot image, injected the appropriate Windows 10 NIC drivers into the boot WIM,
SCCM v1702 HotFix KB4019926 FAILED
By coolslim54,
Installing this hotfix has been a bit problematic. All appears to go well until reaching the "Install Files" section. At that point, it fails and says to check the CMUpdate.log for details. I'll post the contents of the log file. So far, I've redownloaded and reinstalled the hotfix, disabled all antivirus applications on the server, and confirmed SQL permissions were correct. Any advice would be greatly appreciated.
CMUpdate.txt
Bitlocker Pre-provision on wipe and reload
By jcdown,
Trying to figure out if it's possible to get the Bitlocker pre-provision task sequence step to run on a wipe and reload scenario.
-Going Win7 (no encryption) to Win10 (encrypted)
-USMT is hardlinking inside WinPE
-Old Win7 OS (other than hardlinked files) are being wiped (like normal) on "Apply operating system" step
Anyway to make this scenario work?
ADK 1703 Boot.wim Crashes
By jvmorrell,
Hi
So I've updated the ADK on my SCCM server following this guide.
"anotherSCCLWebsite"/how-to-update-windows-adk-on-a-sccm-server/
It now updated to 15063 I then fixed the Secure boot Bug as below
https://blogs.technet.microsoft.com/configurationmgr/2017/04/14/known-issue-with-the-windows-adk-for-windows-10-version-1703/
then replicated the changes using the following powershell script.
https://gallery.technet.microsoft.com/RegenerateBootImageWinPE10-f508f1e4/view/
MBAM Bitlocker encryption befor Logon
By MarciaL,
actually i made a task sequence for MBAM to encrypt all drives - it starts only, when i´m login to Windows 10, but i need it while the tasksequence is running, before starting installing Office 365 and so on. Have anyone experience for this step?
the mbam-client config (last step) set the registry for "no delay" and the mbam-client-Trigger -> reg.exe ADD HKLM\Software\Microsoft\Windows\CurrentVersion\Run /t REG_SZ /v TriggerMBAM /d "%ProgramFiles%\Microsoft\MDOP MBAM\MBAMClientUI.exe" /f
SCCM CB Restore "Recover a site" greyed out
By wanderer,
Hi,
I have a lab setup running SCCM CB 1702, with the SQL instance on the same VM. I want to be able to test restoring a backup from our production server onto this test setup. I have a valid backup but I think I'm doing something wrong. I've tried running the setup from the original iso, from the "splash" in cd.latest and the "splash" in the cd.latest in the backup. Whatever happens on the Available Setup Options page "Recover a site" is greyed out. I've tried stopping the SCCM site u
Clients in secondary site showing only 2 actions, unable to get policy
By Abhijit222223,
Clients in secondary site showing only 2 actions, unable to get policy
Primary Site working fine.
Cas.log error CacheConfig::InitializeFromWmi - GetSWDistSiteSettings failed with 0x80004005. Default site settings will be used
PolicyAgent.log "Skipping request for user policy assignments due to agent configuration for authority 'SMS:"
CAS.log
PolicyAgent.log