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.
- 3 replies
- 4138 views
- Add Reply
- 7 replies
- 5447 views
- Add Reply
- 2 replies
- 2378 views
- Add Reply
- 1 reply
- 3975 views
- Add Reply
- 5 replies
- 8079 views
- Add Reply
- 2 replies
- 2783 views
- Add Reply
- 1 reply
- 6340 views
- Add Reply
In place upgrade 1607 Windows 10 Task Sequence Hanging
By normeyj,
i have begun doing in place upgrade Task sequence at my work. I have set all the models drivers in my task sequence to download and then transfer to a C:\drivers folder based on WMI query. This is working fine and the operating system is downloading as well. What is happening in the SMSTS.log is the task sequence will hang on "RUNNING ACTION: Upgrade Operating System" It hangs running this command and will not move forward and reboot. I am trying to figure out why this is happenin
Problems with Reporting services point
By wingzero,
Hi,
I tried to install the Reporting services point, but i am stuck and do not know where.
I have a sccm server and a seperate sql server.
I configured the reporting services on the sql server.
and i can go to web service url and the web portal url.
then i went to my SCCM server and install the reporting role on my SQL (site system server)
but nothing .....
I thought that the folder which we named while setting up the reporting role should appear in the web portal url
Attempting to display the notification balloon... Notifications not showing.
Branch sites with slow WAN
By teamfox201,
Hello,
Looking for some assistance on getting large packages (task sequence, windows updates, etc) to distribution points with slow WAN speed.
We have about 80 sites averaging 1.5 - 3 mbps back to HQ and we cannot impact their network during the day with SCCM distributions. Currently have the rate limit on those DP's configured to 50% during business hours. With driver updates and Microsoft Monthly Rollup patch bundles growing large in size, it takes forever to get the packages to all th
HP Elite x2 1012 G1 SCCM R2 1607 PXE issue
By rsadmin86,
Recently upgrade SCCM 2012 R2 to 1607. Ever since I have been unable to PXE boot Elite x2 1012 G1 tablets. I can do Probooks no problem. This UEFI thing is really messing me up. Nothing changed in DHCP. The Distribution Point is a 2012 R2 server, so I know that support PXE for UEFI. I am using Realtek USB FE Family Controller v 10.13.1115.2016 in the x64 Boot Image. The Boot Image version is 10.0.14393.0. I see the NBP file being downloaded successfully, quickly blips to another message, and goe
Distribution Download of image.wim slow
By JeremyLeirmo,
Hello,
I have recently encountered extremely slow download of the Image.wim files while in PXE environment.
I have verified that IIS is not being limited and in monitoring the switch port the server is connected to I have getting on between 8-10% utilization of the 1GB port and the Server Resource monitoring is showing a max network at 100Mbps. The Image.wim file is 8.2GB and is taking roughly 6-7 hours to download.
This is not a question about TFTP transfer of the Boot.wim and have in pla
Unable to import new bootimages
By surfincow,
Hello,
After I upgraded ConfigMgr to 1610, I found none of my Windows 7 task sequences are able to complete. They fail at the "add driver" step and I believe it is due to the fact that the latest ADK 10.1.14393.0 is not backwards compatible with Windows 7. Since the ADK that is compatible with Windows 7 is not compatible with Windows 10 I had left the original working boot images for Windows 7 deployments and created a new boot image on the new ADK for Windows 10.
Unfortunately during th
How to handle client compliance issues/errors
By dinci5,
Hi there,
Recently we upgraded from SCCM 2012 to 1606 Current Branch.
Most clients are updated successfully.
I have some of them that are Failed.
As show here:
However, when I look at the details, it's hard to understand why.
The correct client version should be: 5.00.8412.1307
In this screenshot you can see some clients that have the Failed status.
Client Version Reported From DDR has the correct version.
Client Version Reported From FSP/MP has the wrong ersion.