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.
- 1 reply
- 1481 views
- Add Reply
- 1 reply
- 1472 views
- Add Reply
- 0 replies
- 2603 views
- Add Reply
- 1 reply
- 1637 views
- Add Reply
- 1 reply
- 1401 views
- Add Reply
- 3 replies
- 2509 views
- Add Reply
- 1 reply
- 1395 views
- Add Reply
- 4 replies
- 1805 views
- Add Reply
Just installed 1810 upgrade, not seeing LifeCycle Report
By jamesmm,
I just installed the 1810 update and was looking through the 'What's New in 1810' post. I came across the item about LifeCycle Report 'LifeCycle 05A', but I don't see that report listed in my Reporting folder under Monitoring.
Is there a way to get that report ? I am thinking if I remove/re-add my Reporting Point? But if I do that, I will probably lose any customized reports?
thanks,
James
USMT Node Empty
By Manuel De Sousa,
Hey everyone,
Im hoping someone out there has had a similar issue and can provide assistance. Here are our versions
SCCM CB 1806 Build 8692
Using USMT 5.0 on Windows 10 1803
Leveraging SMP on SCCM.
The whole process is working as expected. The users state gets uploaded to the server, and then restored back on to the PC through the rebuild task sequence.
What isn't working is the USMT node in SCCM. It is always empty. We had a machine listed once, but I have not been able
Failed to get client identity (80004005) - after CM 1810 upgrade
By dinci5,
Hi,I have upgraded my lab to 1810 recently. And I think something is broken.The lab is setup in Hyper-V and used to work fine before.Ever since I've upgraded, my deployments are not working.A couple of errors from smsts.log:"Network access account credentials are not supplied or invalid.""Failed to get client identity (80004005)""failed to request for client""SyncTimeWithMP() failed. 80004005.""Failed to get time information from MP: http://LAB-CFG.Domain.com."Now, I've seen this error before in
OSDComputerName issue
By KeithDib,
Guys
Been building Windows 10 1709 for about a year all fine... We are starting to build 1809 and all works except the TS/Naming now seems to ignore the Collection Variable 'OSDComputerName'
I have both 1709 and 1809 images, both building from the same 'All Unknown Computers' collection, the 1709 works the 1809 does not. the 1809 uses a copy of the TS from 1709 with just the WIM changed.
Any ideas?
thanks
Report Subscription for Hardware Inventory completion
By xerxes2985,
I am trying to create an email notification that will report all the systems that completed their hardware inventory (which occurs daily) and those that haven't, and send an email notification with the status.
Is this possible?
Thanks
SCCM 1810 Application Approval Request Emails
By mhedden94,
Been checking out the new email approval feature for application requests in CB1810, however, I am running into an issue and can't seem to figure it out. To start, I can successfully request an application and SCCM triggers the alert and I successfully receive an email. However, when I attempt to approve or deny the request, I get a website security error and can't proceed. I am not using Azure integration and I am attempting this on my local intranet. Any ideas? (Sensitive information remo
PXE error
By rustam_sh,
Hello, guys!
I have a problem with my SCCM 1806 Primary Site enviroment in attachment.
I already reinstalled PXE, WDS twice, recreated all boot images at Primary SCCM server
But it didn't helped.
Same time we have additional site server distribution point whith PXE enabled at other office and same task sequence works just fine without any error.
All boundaries and DHCP options configured well.
I don't have a clue what to do else.
Please help.
Thanks in adv
Definition updates wont be applied to windows 10 Clients
By Christoffer Mikkelsen,
Hi There!
Christoffer here, worked with SCCM for 2 Years!
We have a customer who is running sccm 1806 - clients is minimum 1709.
Our problem is, that definition updates wont be applied to the windows 10 clients.
It startet to occur, after i installed a new standalone 2016 WSUS server, identical to their old 2012.
If i run the initial synchronization for the ADR i can see, almost all computers have a Group policy conflict, and from what i can read, it comes down