WSUS Error 2149842967

When installing patches and hotfixes silently (wusa.exe <some_patch_or_hotfix.msu /quiet /norestart) it is advisable to check the Setup eventlog.

It is possible that you find some error there:

Windows update could not be installed because of error 2149842967

Actually what Windows is saying:

The update is not applicable to your computer.

Well oke that could also be in normal English 😉

Microsoft Application Virtualization 4.6 SP3 is now supported on System Center Configuration Manager

System Center Configuration Manager 2007 SP2 and System Center 2012 Configuration Manager SP1 now support Microsoft Application Virtualization (App-V) 4.6 SP3 Desktop Client and Application Virtualization Client for Remote Desktop Services. This client release enables support for Windows 8.1 and Windows Server 2012 R2.

No software updates are required.

As per Microsoft source: http://blogs.technet.com/b/configmgrteam/archive/2014/01/24/microsoft-appv-4.6-sp3-is-now-supported-on-system-center-config-mgr.aspx

Can’t connect to C$, ADMIN$ or any administrative share on workstations

If you are attempting to access a Windows 7, Windows 8, Vista or Server 2008 (R2), Server 2012 (R2) computer you may get  the” Access Denied – Failed to connect to ADMIN$ share” error , even when supplying the appropriate local user credentials that have Administrator access. If the target computer is not a member of a Windows 2003 or later Domain then this is most likely because the target system has Remote UAC enabled. Remote UAC prevents local administrative accounts from accessing ADMIN$. (more appropriately Remote UAC prevents local accounts from running in an elevated mode when connecting from the network) If you need to be able to access the ADMIN$ using a local account then you will need to disable Remote UAC. You can accomplish this by editing the registry.

Assuming you have all your other ducks in a row (Firewall exceptions, appropriate credentials of local administrative user, etc) then you just need to add a quick entry in the registry of the target computer. In the registry, navigate to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.

Create a DWORD value called LocalAccountTokenFilterPolicy and assign it a value of 1.

You then can restart the Server service (but a reboot would be ideal ;-)).

cant't connect to admin$ or administrative share

LocalAccountTokenFilterPolicy

* By default, when local credentials are used to access a Windows Vista (or later) system that is a member of a Windows Domain this problem does not exist. Your Windows domain may still disable Remote UAC.

** By default Remote administrative access is denied to local accounts when a Windows Vista (or later OS) is NOT a member of a Windows 2003 or later domain.

Microsoft info:

http://support.microsoft.com/kb/942817

http://support.microsoft.com/kb/951016

The task sequence has failed with the error 0x80070570 – ConfigMgr 2012

I was in the process of deploying an OS with ConfigMgr 2012 R2 when I saw this error:

The task sequence has failed with the error 0x80070570

Hmm, well oké what is this then?

Task sequence starts, disk gets partitioned, image is downloaded and then this.

So after a little search I found

0570 = 1392 = “The file or directory is corrupted and unreadable.”

This could be issues or corrupt data on Distribution Points. This was not the error in my case. It also could be that the downloaded image was getting corrupt during the download. Also not the issue!

Then I tried to wipe the disk in WinPE with DiskPart:

 

Then I started the deployment again et voila! Everything started working again J

So with a 0x80070570 Error always check your disk partitioning.

Configuration Manager 2012 R2 Hotfixes

SCCM 2012 R2 has some hotfixes you might need:

2905002

An update is available for the “Operating System Deployment” feature of System Center 2012 R2 Configuration Manager

This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.

Issue 1

After you enable the PXE Service Point role (http://msdn.microsoft.com/en-us/library/jj217832.aspx) on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running. Additionally, entries that resemble the following are logged in the Windows Application log:

Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3

Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a

Exception code: 0xc0000005

Fault offset: 0x000000000005f61a

Faulting process id: 0xae4

Faulting application start time: 0x01cec5d767184634

Faulting application path: C:\Windows\system32\svchost.exe

Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll

Note This problem affects only distribution points that are installed on site servers.

Issue 2

When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows operating system.

2907591

Per-computer variables for imported computers are not read in System Center 2012 R2 Configuration Manager

Per-computer task sequence variables that are defined for imported computers are filtered out of client policies. This prevents the variables from being read during task sequence execution. This problem does not affect per-computer variables that are defined for existing clients.

2907566

November 2013 anti-malware platform update for Endpoint Protection clients

This anti-malware platform update contains the following improvements:

  • Adds anti-tampering functionality to reduce the risk that malware will disable or bypass anti-malware scanning.  For example, access to files and folders that are used by the anti-malware platform can be changed only by trusted system processes or by the anti-malware platform itself.
  • Improves overall performance of the anti-malware platform. Anti-malware performance is improved compared to that of previous platform versions. Improvements were made to scan functionality. These changes involve no configurable effects.
  • Ongoing improvements to Microsoft Active Protection Service (http://technet.microsoft.com/en-us/library/ff823779.aspx) (MAPS) and Dynamic Signature Service (http://technet.microsoft.com/en-us/library/ff823908.aspx) (DSS). These make real-time cloud-based protection easier. Scale and performance improvements were made to the MAPS and DSS systems. Make sure that you opt-in to at least Basic or Advanced MAPS to make sure that you are benefitting from cloud-based protection.