Jump to content


Mark C

New Members
  • Posts

    5
  • Joined

  • Last visited

Mark C's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. Version 2603 with KB38232642 and KB37942646. Running in EHTTP. Servers also have web certificates bound on HTTPS issued by our domain certificate authority server.
  2. I've reinstalled the MP on one server and the Critical error 0mb appears straight away. Firewalls are disabled on the servers. There no errors showing in the message log for the MP, no errors on the MP log files, mpmsi.log and mpsetup.log On the site server, there's no errors in sitecomp.log or statmgr.log,. sms_site_system_status_summarizer.log doesn't exist. hman.log shows Error: Could not create certificate binary Failed to sign User Service Certificate for <server> of site There's no errors in the mpcontrol.log. Http test request succeeded. There's no Https test and SSL is showing in the log not enabled.
  3. I've upgraded our configuration manager server OS from 2019 to 2022 and after running the CM reset and reinstalling wsus the main server and distribution points are all working, however all the management points apart from the CM server are showing critical and 0mb under Site Status. The message log is showing Site System Status Summarizer detected that the storage object on site system has 0 KB of free storage space, which is less than or equal to the Critical Free Space Threshold of 5242880 KB. The error only occurred after the OS upgrade, there's space on the servers which also act as distributions points which show the correct space in the site status. Removing and reinstalling the MP role hasn't made a difference. Currently the MP role has been removed from the servers so the clients can communicate.
  4. I think I've now found the cause, the apply operating system task is using the variable OSDisk which as it isn't in the Powershell script I've set a set variable task, however it was set to C and in the BDD.log it is showing as c:
  5. We currently have MDT integration with Configuration Manager, however due to Microsoft no longer developing MDT and vbscript being removed in the future, I've being reviewing our Task Sequences. I've been able to remove MDT from the base metal pxe boot TS and it works, however we also use the Refresh Only part of the MDT TS which as an 0x80070057 when the TS starts the Apply Operating System. I've replaced the MDT Gather task with powershell script from GitHub - jonconwayuk/PowerShell_Gather: PowerShell script to replace MDT Gather in Windows OSD which doesn't work. The TS only works if I add the Use Toolkit Package and Gather tasks for MDT which then allows the TS to wipe the C drive and apply the wim file. I presume the MDT Gather is setting a variable that the Powershell script doesn't.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.