Posts

Showing posts with the label WSUS

SCUP, WSUS, Dell and Error 0x8024000f

-
Update: See bottom of post for another variation on this. Now here was a real barrel of laughs to track down and fix. The setup: Import the Dell Client catalogs into SCUP 2011 Publish them all to WSUS with automatic (effectively metadata only) Check for updates from a client machine Get Error 0x8024000f in Windows update Upshot of this is that WSUS is broken and by extension, so are software updates via SCCM. The culprit? Circular references in Dell's update catalog. How to fix: Turn on verbose logging for WSUS on a client PC  http://support.micro...723#letmefixit2 Check for updates Open c:\windows\windowsupdate.log Search for the word "cycle" Get the update ID that has the circular reference Find that update in SCUP and expire it (you may want to fix it, but I didn't bother as I don't need the affected updates) Publish the update again Go back to step 2 and keep repeating until Windows Update on the client PC works (I had about 8 wi...
1 comment
Read more

When SCUP 2011 Cleanup Wizard won't clean up...

-
In SCUP 2011, there's the Software Update Cleanup Wizard which will remove from WSUS any updates that are no longer in SCUP. Only one problem: if the update exists in WSUS, but the content isn't in UpdateServicePackages, the clean up fails as it can't verify the signature of the cab file. As the wizard doesn't care about the content of the file, it's quite easy to fool it. Open SCUP.log and find the error Create a folder in UpdateServicePackages that matches the folder of the missing content. e.g. \\WSUS01\UpdateServicesPackages\7d0f53e4-482e-462d-b81b-127941c32091 Find an existing cab file within the UpdateServicePackages folder and copy it into your new folder Rename the copied cab file to the name of the missing cab in the SCUP folder Run the SCUP Cleanup Wizard again Clean up success! Seems like a bug to me as removing the entry from the WSUS database shouldn't really care if the content exists.
Post a Comment
Read more

Popular posts from this blog

Avoid Microsoft Intune if you use G-Suite and Android

-
Like me, you might have considered Intune to be your one stop MDM solution if you're an Office/Microsoft 365 user. On the whole it is pretty good, but it's got one massive failing: It doesn't support Google accounts on Android Work Profiles. You might think that if you're a Microsoft shop it's not a big deal, but there two major reasons why you might want to use Google alongside Azure Active Directory: SSO. Many companies charge extra for SSO with Azure but include it for free with Google, e.g. Slack and Atlassian. Chrome. Let's face it, everyone uses Chrome rather than Edge so signing in with a Google account to sync your favourites is pretty handy. Managing this setup in an organisation is pretty easy. Sign up for G-Suite account, sync all your users from Azure AD, configure G-Suite to use AAD for authentication and you're done. Enterprise managed Google accounts for everyone at zero cost if you don't actually need G-Suite. Given the abo...
Read more

Setting Wallpaper for a Remote Desktop Session

-
Ah, the fun I had trawling around trying to find out how to set the wallpaper on a remote desktop session! The (seemingly) most obvious answer was changing the Wallpaper setting under Desktop in a GPO, but no. That setting explicitly states that it doesn't apply to RDP sessions, so back to the registry we go... I'm presuming here that we want these settings to apply to all the computers within a specific OU rather than to individual users. Create a new GPO "Wallpaper" Navigate to Computer Config/Policies/Admin Templates/System/Group Policy Set "Configure user Group Policy loopback processing mode" to Enabled with Mode as "Merge" Navigate to Computer Config/Policies/Admin Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Remote Session Environment Set "Always show desktop on connection" to Enabled Set "Enforce Removal of Remote Desktop Wallpaper" to Disabled Navigate to Computer Con...
Read more

DFS "Waiting for Initial Replication"

-
Taken directly from  Technet Forum  post by  scorprio_milo . Pop along and give them an up vote! You may encounter the error message "waiting for initial replication" when no primary member is currently specified on the DFS Replication. This DFS member is waiting for initial replication for replicated share folder Public and is not currently participating in replication. This delay can occur because the member is waiting for the DFS Replication service to retrieve replication settings from Active Directory. After the member detects that it is part of replication group, the member will begin initial replication.  Besides, there is also possiblity that DFS servers cannot contact domain controller which could result in the issue. 1. Please first verify that all the target folder of Public folder is enabled.   2. Please use Dfsradmin to set the primary member in the situation where there is an existing replication group that is waiting...
Read more