AlteredAdmin

We are looking to overhaul our software request and renewal process. What is your approach to this? Since we operate in the education sector, schools often use a wide range of software. How do you track these applications? I understand that the process can involve both IT and purchasing approvals. We’re mainly looking for different perspectives to see how others manage this. Could you provide a high-level overview of your process? Thanks, AA

This is the script that i use: https://github.com/AlteredAdmin/Microsoft/blob/main/Windows%20Updates/Reset_Windows_update.ps1 More information: https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/additional-resources-for-windows-update

So it appears i may have solved my issue. I deleted all files in C:\Windows\Servicing\Packages\ that i had permissions to delete. Mostly all the .MUM files. If i had to do it again i would only delete the effected one. Ran the Windows Update fix script to clean house. Rebooted, Checked for windows update failed Checked again and was able to install the 2023-01 Cumulative Update for Windows Server 2019 for x64-based Systems (KB5022286)

Server info: OS Name: Microsoft Windows Server2019 Standard OS Version: 10.0.17763 N/A Build 17763 Original InstallDate: 1/17/2020, 12:25:18 PM Having issuesinstalling cumulative updates. It seems to have installed defender and .NETupdates fine. But can't get the current (Win 10 (1809) and Server 2019 -Cumulative Update (64-bit) January 10 2023) or previous December update toinstalled. If I try it manuallyit fails with MSI failed with error code -2146498304. When I try it fromWSUS or Microsoft it fails with 2023-01 Cumulative Update for Windows Server2019 for x64-based Systems (KB5022286) - Error 0x800f0900 I have tried toreset windows updates according to the below KB. https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/additional-resources-for-windows-update Ran the SFC /Scannowand the DISM restore health commands The restore health command fails withError: 0x800f0954 In Googling allthese error codes I'm basically chasing my tail. Everything keepscircling around to the same thing over and over and nothing seems to work, andeverything fails The below is from the windows update log. [font=Calibri]2023/01/1311:00:13.1374595 7128 8128 Handler CBS called Error with 0x800f0900, [/font] [font=Calibri]2023/01/1311:00:13.1402237 7128 8128 Handler CBS called Terminate[/font] [font=Calibri]2023/01/1311:00:53.9164837 7128 7556 Handler Completed install of CBS update withtype=0, requiresReboot=0, installerError=1, hr=0x800f0900[/font] [font=Calibri]2023/01/1311:00:54.0648649 7128 7556 Handler * END * CBS Install[/font] [font=Calibri]2023/01/1311:00:54.6929704 3664 5204 Agent *FAILED* [8024200B] Method failed[CAgentUpdateManager::InstallUpdate:11739][/font] [font=Calibri]2023/01/1311:00:54.8788666 3664 5204 Handler Loaded state: cCompleteIterations: 1,pt: SelfContainedNoExpressPayload, nNextRequestID: 1.[/font] [font=Calibri]2023/01/1311:00:54.9012256 3664 5204 Agent LogHistory called.idUpdate={447FF6C5-74A0-4DFD-A497-9039E898E010}.200, resultMapped=800F0900,resultUnMapped=800F0900[/font] [font=Calibri]2023/01/1311:00:54.9131342 3664 5204 Agent Install updates CallerId =UpdateOrchestrator[/font] [font=Calibri]2023/01/1311:00:54.9132320 2116 4776 ComApi Install ClientId =UpdateOrchestrator[/font] [font=Calibri]2023/01/1311:00:54.9140489 2116 4776 ComApi Install call complete (succeeded = 0,succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0[/font] [font=Calibri]2023/01/1311:00:54.9143000 2116 4776 ComApi Reboot required = False[/font] [font=Calibri]2023/01/1311:00:54.9143085 2116 4776 ComApi Exit code = 0x00000000; Call errorcode = 0x80240022[/font] [font=Calibri]2023/01/1311:00:54.9143100 2116 4776 ComApi * END * Install ClientId = UpdateOrchestrator[/font] [font=Calibri]2023/01/1311:00:54.9146923 3664 1652 Agent WU client calls back to install call{36B49B40-ED6B-4C7D-A74A-D2CC913B7D67} with code Call complete and error 0 [/font] [font=Calibri]2023/01/1311:00:54.9149632 2116 6932 ComApi Install call complete (succeeded = 0,succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0[/font]

Good morning, I have a print server running on server 2019. The print spooler is not stable. It keeps restarting, the only way i have gotten it working is to set Subsequent Failures to restart the service. The service will restart between 3-5 minutes. during this time one can print no issues. I think its a corrupted or outdated print driver. The drivers that are in use range from 2018 - 2006. So yea i would say their are some really old drivers on their. I know the print spooler is crashing but i cannot find what exactly the cause it. the event viewer has not been much help i have posted the errors i see below. Is their a process to track down the driver? Everything i read online just said to update all the drivers but nothing about tracking the down the exact one that is causing it. Aside from having Techs do a Clean up on the server, Update Currently used drivers, Remove unused/old Drivers and delete old queues. If that does not work the only other thing i can thing od is to build a new server and install everything fresh and manually move printers over. Their are 78 drivers Their are 81 Printers Thoughts?? I see the below but those files don't exist, which is why i says "The print spooler failed to delete the file" The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\prnms003.inf_amd64_9bf7e0c26ba91f8b.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\prnms002.inf_amd64_4d944e2fb3bcc43c.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\x64\PCC\ntprint.inf_amd64_18b0d38ddfaee729.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\W32X86\PCC\prnms003.inf_x86_dd2fd5b05c3d8604.cab, error code 0x2. See the event user data for context information. The print spooler failed to delete the file C:\Windows\system32\spool\DRIVERS\W32X86\PCC\ntprint.inf_x86_18b0d38ddfaee729.cab, error code 0x2. See the event user data for context information. I see this from time to time but it does not tell what the print driver is.... Document failed to print and was deleted because of corruption in the spooled file. The associated driver is: . Try printing the document again. Not much i could find out but about the below The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21-636618257-2613738635-33974680-1377919\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable. I see this every 3-5 minutes... The Print Spooler service terminated unexpectedly. It has done this 12 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. And yes i know about Cleaning out C:\Windows\System32\spool\PRINTERS but this is the not the case as it will stop while that is empty/ no jobs coming in. Thanks

we had a cert expire and when it was renewed. VCenter shows the PowerStore VASA provider offline and the storage shows off line. WE found a KB that says to recreate the VASA provider on the Vcenter side. But what happens when one does that, what happens to the vms running on the Vvol? But what happens to the Vms on the Vvols that the VMs are off. obviously when its offline in Vncent one cant create VMs on it or mange it. but happens the current Vms when its deleted and recreated? We cant find any information on what happens after its recreated.... I don't have the KB in front of me. but will post it when i do. Vmware support has not been much help in this matter... Thoughts?

So i keep thinking that a node votes in the same way that witness does. But starting to think that is not the case. For example all nodes votes are special, but a witness's vote is extra special?

Afternoon, Fail over cluster if Cluster managed voting is Enabled do you still need quorum witness? The reason i ask is because we set up a 3 node cluster but still get the "The cluster is not configured with a quorum witness. As a best practice, configure a quorum witness to help achieve the highest availability of the cluster." on validation even though Cluster managed voting: Enabled if a witness is needed for 3 nodes how is that different from 2 nodes with a share witness? This will be used for SQL.Thoughts? This will be used for SQL.

we will add another partition if its needed, some of servers are just small application servers and don't need a lot of space.

Good morning We use VMware templates to create servers. We noticed that after installed windows server 2022 the recovery partition is after the C: drive.This can create issues when the C drive needs to be expanded. IS it safe just to delete and remove the recovery partition so C: can have room to expand?Would doing this cause ay future issues? Aside from needing the recovery partition. And could one just make a bootable DART disk if it was really needed?We never use the recovery drive, because we have snapshots backups and most of the time we would just rebuild the server. Thoughts?

The basic Question is Does MDT support windows 11, i ask because when looks at the Microsoft documentation windows 11 is not listed.... is it not officially supported? Or did they forget to update the docs? https://docs.microsoft.com/en-us/mem/configmgr/mdt/release-notes#supported-platforms The reason i ask, is as we move away from SCCM to Intune, we would like a quick way to PXE and image a machine and install the Intune enrollment package (For machine that don't have an OS or need a clean install), and was wanting to use MDT. Does Microsoft plan to continue to support MDT?

Good morning i have some questions about the Update Microsoft Defender for Endpoint core components Security Recommendation. Windows Server 2016 64-bitVersion 1607 I have done update path 2 as the servers that seem to be effect are 2016. I have installed the onboarding package that installs Microsoft Defender for Endpoint and ran the onboarding script. the Microsoft Monitoring Agent is still installed. I have also ran all windows updates so the server is fully patched. However that security recommendation does not go away. I know sometimes you have to give it 24 hours before that list updates, but the other security recommendation have fell off since i have done them. How come this still lingers around? Does any one else have this issue? Is their something I'm missing? ======================= DescriptionIndicates that the Microsoft Defender for Endpoint EDR sensor (Windows Server 2012 R2, 2016) or Microsoft Defender for Endpoint agent (Linux, macOS) installed on the machine is not up to date.Windows Server 2012 R2 and 2016 If you’re currently running the legacy Microsoft Defender for Endpoint agent solution (based on the Microsoft Monitoring Agent - MMA) with MsSenseS.exe version 10.3720.*, please skip directly to Update path 2. Update path 1 Update the latest EDR sensor version described in Microsoft Defender for Endpoint update for EDR Sensor using one of the following methods:Windows UpdateA patch management solution such as WSUSDownloading and applying the package from the Microsoft Update Catalog. Update path 2 This option only applies if you’re currently running the legacy Microsoft Defender for Endpoint agent solution (based on the Microsoft Monitoring Agent - MMA) with MsSenseS.exe version 10.3720.*, in which case you will first need to upgrade to the new solution by following these steps:Go to the onboarding page in the M365 Defender portalSelect the ‘Windows Server 2012 R2 and 2016 (Preview)’ operating systemsChoose your preferred deployment methodDownload the installation and onboarding packagesInstall the package and apply the onboarding script via your chosen deployment channelOnce the new solution has been installed, future updates should be done by following the instructions described in Update path 1.For additional information on what’s new and how to install, including applying Defender Antivirus passive mode configuration if you’re using a non-Microsoft antimalware solution,please refer to Onboard Windows servers to the Microsoft Defender for Endpoint service | Microsoft Docs.

Outlook Client Forwarding email question | The FROM: Flied does not have "Name <[email protected]>" When users are using the outlook client Microsoft outlook 2019 MSO build 16.0.10383.20027 when they click forward on an email the section that contains FROM SENT TO CC the TO and CC will have the persons name and <[email protected]> but the FROM section will only have the persons name. I don't think the version number of the client matters cause different users on different versions of outlook have this happen, seems to happen from what type of office install they have. This only appears to happen with the FROM when its a internal person. External people have the For example the FROM does not have the From: Doe Jr, John D. Sent: Monday, March 21, 2022 11:17 AM To: doe, bob M. Cc: doe, jane S. Subject: RE: This is a test email We also found depending on how you access outlook you can different results. Outlook web From: name From: Name Outlook web X Outlook 365 (installed from Intune) X Outlook Mac version X Outlook installed from SCCM using https://config.office.com/ X Supporting links: https://answers.microsoft.com/en-us/outlook_com/forum/all/when-i-manually-forward-an-email-i-lose-the/35c63028-e033-43c8-b103-98cf172ac1e8 https://answers.microsoft.com/de-de/outlook_com/forum/all/forwarding-an-email-removes-original-senders-email/4cac943f-b329-4dc1-9838-ecc24cd6a7fe?messageId=4eb83537-0d8e-4166-8c1f-74b3991e8c2c https://support.microsoft.com/en-us/topic/email-header-only-displays-the-display-names-of-the-recipients-but-not-their-email-addresses-in-outlook-2013-d5260110-dfb3-4a2b-92a4-468d1d69afd3 Those links contain people with similar issue . Thoughts as to what is going on?

Also on the devices what do you have set for "Enable Automatic MDM enrollment using default Azure AD credentials"? Does that need to be set if you are using provisioning package.

Ok i was able to get the package to install on a on prem domain joined machine, and it is both domain joined and Azure AD joined according to dsregcmd. I was able to figure out the naming thing https://deviceadvice.io/2021/04/06/exploring-hybrid-azure-ad-join-with-a-provisioning-package/ The device does show in Azure AD and on prem AD. However the device does not show in Intune. Am i missing something?