Jump to content


hecke1234

Established Members
  • Posts

    6
  • Joined

  • Last visited

hecke1234's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I don't understand the issue, but I was able to fix it. The user which I use for my wsus and proxy connection "lost" all permissions for the database. I found the failed db-logins in wsyncmgr.log. After I fixed the permissions I can see all Office 365 Updates. The funny thing is, that all other updates for win 7/10 and server products syncd very well!? idk now it works
  2. Hi Comm, I'm using SCCM 1802 with all hotfixes and after serveral wsus syncs, there are some updates missing for x64 or x86 architecture. In my case I need the 1807 (10325.20118) Update for x86, but it's only the x64 version available. I've never seen this before for other products like older Office versions or Windows in my environment and found no known issue for this. Has someone an idea or seen this before?
  3. Hmm, then I will suppress all reboot messages.
  4. I think there is no way to rollback over the update deployment component. I would just create an application to uninstall it like "wusa /uninstall /kb:{update ID}"
  5. Hi Community, I have some issues with the reboot message behavior. I get the normal reboot countdown from the software center, but there comes a second popup 10 minutes before reboot. This popup has the wrong date and time format for my german clients. The client regional settings are set to DD.MM.YYYY. 2 minutes before reboot comes a second popup with correct time format. The popup process is wlrmdr.exe. My favorite solution would be to suppress this popups and only to show the software center countdown. Or is it possible to fix the date/time format? Thanks in advance!
  6. Are you talking about a Windows/Office update?
×
×
  • 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.