SCCM Agent Issues - CCM Agent Notification Agent Disabled
Had issues with a CM Agent on a computer. This agent installed with BITS transfers in foreground:
ccmsetup.exe /BITSPriority:FOREGROUND
The agent wouldn't install normally.
After installed, the component "CCM Notification Agent" was stuck at status Disabled in the Configuration Manager Properties.
Found this in DataTransferService.log:
CDTSJob::HandleErrors: DTS Job '{4C558D5D-CA3F-4712-9483-5E3BBF7D811C}' BITS Job '{B02B8C90-482B-47C6-BBC1-2397BEA72C64}' under user 'S-1-5-18' OldErrorCount 16 NewErrorCount 17 ErrorCode 0x80070426
CDTSJob::HandleErrors: DTS Job ID='{4C558D5D-CA3F-4712-9483-5E3BBF7D811C}' URL='http://SCCM02.domain.com:80/SMS_MP' ProtType=1
The following forum gave me the idea to look into the BranchCache service:
Running the command "bitsadmin /list /allusers" listed a bunch of errors:
{4BD1CBD5-C107-49D7-A478-A4EEAD87E098} 'CCMDTS Job' TRANSIENT_ERROR 2 / 30 10868 / 271558
{B02B8C90-482B-47C6-BBC1-2397BEA72C64} 'CCMDTS Job' TRANSIENT_ERROR 2 / 6 164302 / 266990
Found out that the BrancheCache service was set to Disabled.
After changing the service to Manual and starting it, the agent went up and running perfectly.
Hope this helps someone out there!
Cheers
Distribution Point Configuration Status - SMS Client - Restart might required
Annoying message that doesn't go away even after a restart.
To remove it:
ConfigMgr collections update slowly or not at all
Please read the following article if you're experiencing this.
Cannot backup DPMDB after upgrading to DPM 2012 R2
After updating to DPM 2012 R2 the DPMDB says Agent unreachable in the Protection area in DPM. Looking in the Event Viewer - System Log, there is the following two error messages:
Source: DistributedCOM
Event ID: 10005
DCOM got error "1053" attempting to start the service DPMRA with arguments "Unavailable" in order to run the server: {DA6AA17A-D61C-4E9C-8CEA-DB25DEA52A95}
Source: Service Control Manager
Event ID: 7009
A timeout was reached (30000 milliseconds) while waiting for the DPMRA service to connect.
If you try to start DPMRA.exe manually in a command prompt it says that VssRequestor.dll is missing. After copying this file from another server (C:\Program Files\Microsoft Data Protection Manager\DPM\bin\VssRequestor.dll) to C:\Program Files\Microsoft System Center 2012\DPM\DPM\bin the DPMRA starts successfully.
Unable to upgrade DPM to 2012 R2
When launching the DPM 2012 R2 update I get stuck at the first step, checking prereqs. The error message says:
The instance provided is not a SQL Server instance. Please provide a SQL Server instance.
Looking at C:\Program Files\Microsoft System Center 2012 R2\DPM\DPMLogs\DpmSetup.log, I found the following error messages:
[11/13/2013 10:03:06 AM] Information : Querying WMI Namespace: \\dpm01\root\Microsoft\SqlServer\ComputerManagement10 for query: Select * from SqlServiceAdvancedProperty where ServiceName='MSSQL$MSDPM2012' and PropertyName='Version'
[11/13/2013 10:03:06 AM] * Exception : => System.Management.ManagementException: Invalid class
[11/13/2013 10:03:06 AM] Information : Getting the error code for check : SqlServer and result : 67141632
[11/13/2013 10:03:06 AM] Information : Found Error Code:SqlNotInstalled and Severity: Error
[11/13/2013 10:03:06 AM] Information : Got Error Message: The instance provided is not a SQL Server instance. Please provide a SQL Server instance.
[11/13/2013 10:03:06 AM] Information : Got Error Message: The prerequisite (SQL Server 2008) required to perform this check is missing.
As you can see the error messages states that we're asking for an invalid class when querying the wmi namespace. So we need to recompile the SQL WMI provider with the following command:
mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
After doing this, the upgrade proceeds normally.
Also, an important thing to mention is that with R2, DPM no longer supports backing up Windows Server 2003!
Software Updates Synchronization Failed
From time to time the software update synchronization fails in Configuration Manager. Been looking around the web for a solution, but haven't come across anything.
In my particular case, these error messages appeared in wsyncmgr.log:
Sync failures summary:
SMS_WSUS_SYNC_MANAGER 2013-10-31 11:06:04 9804 (0x264C)
Failed to sync update 359c5eeb-b7ff-447a-9986-5d6283a133f3. Error: The Microsoft Software License Terms have not been completely downloaded and cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow SMS_WSUS_SYNC_MANAGER 2013-10-31 11:06:04 9804 (0x264C)
Failed to sync update 5e174b97-938e-41b7-9428-b2f9978ddd2d. Error: The Microsoft Software License Terms have not been completely downloaded and cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow SMS_WSUS_SYNC_MANAGER 2013-10-31 11:06:04 9804 (0x264C)
Failed to sync update 87e13ecb-c669-43be-9e2a-01e567285031. Error: The Microsoft Software License Terms have not been completely downloaded and cannot be accepted. Source: Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow SMS_WSUS_SYNC_MANAGER 2013-10-31 11:06:04 9804 (0x264C)
Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates SMS_WSUS_SYNC_MANAGER 2013-10-31 11:06:05 11924 (0x2E94)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=sccm.domain.se SITE=P01 PID=4180 TID=11924 GMTDATE=to okt 31 10:06:05.267 2013 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates" ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 2013-10-31 11:06:05 11924 (0x2E94)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 2013-10-31 11:06:05 11924 (0x2E94)
After googling "359c5eeb-b7ff-447a-9986-5d6283a133f3" I found out that the affected updates are Internet Explorer 10.
I also found this in the Event Viewer:
Content file download failed. Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Source File: /msdownload/update/v5/eula/use_terms_supp_ie10_win7_rtm_en-us.rtf-f1a39475-6df8-45fe-848f-298e9965f6e7.txt Destination File: e:\Sources\WSUS\WsusContent\C2\4DE69528CE193088F812466D6AE27184026C58C2.txt.
At first I thought the two were related to eachother, but I found out later that they're not. The later error message is solved by adding NETWORK SERVICE with read permissions to the WsusContent folder.
As we're not running Internet Explorer 10 in our company, I solved the first problem by declining those three updates in WSUS. If anyone has a solution on getting the License Terms to download, please comment this post. The updates can be found in WSUS by sorting the updates by the Status Rollup column.
Cheers!
OSDisk appears as D:
This has been driving me totally crazy for a while! Finally I found the solution, which is always simple when you know it.I've been trying to deploy the original install.wim from the Windows 7 media with SCCM 2012, and every time, OSDisk appeared as D:.First of all, you should select "Apply operating system from an original installation source" in the "Apply Operating System Image" task. You should also have the "Set Variable for Drive Letter" set to False. Both settings are found in the Install section.The last and final setting, that took me a while to find, was in the Preinstall section and the task "Format and Partition Disk 6.1". For some reason, Microsoft has left the "Do not assign a drive letter to this partition" unticked for the BitLocker BDEDrive.I hope this helps someone out there...Cheers!
Issues updating to Exchange Service Pack 2
Event ID: 1310Source: ASP.NET 2.0.50727.0Exception message: Could not load file or assembly 'Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:Program FilesMicrosoftExchange ServerV14ClientAccessAutodiscoverweb.config line 940) C:Program FilesMicrosoftExchange ServerV14ClientAccessAutodiscoverweb.configC:Program FilesMicrosoftExchange ServerV14ClientAccessPowerShellweb.configThe transport process couldn't load poison message information from the registry. Access to the registry failed with the following error: Access to the registry key 'HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServer14TransportPoisonMessageBootProcess' is denied.Administrators: Full ControlSystem: Full ControlNetwork Service: Full Controlhttp://technet.microsoft.com/en-us/library/ff360361(v=exchg.140).aspxThe Pickup directory doesn't have permissions to write the pickup location to registry (HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServer14Pickup). Please make sure Network Service has Full Control to the registry location. The error was System.UnauthorizedAccessException: Access to the registry key 'HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServer14Pickup' is denied.Ran a Health Check with exbpa'ClientAccessRole' not configured'HubTransportRole' not configuredEnded up with System Center Endpoint Protection being the issue. Added %ProgramFiles%MicrosoftExchange Server in the exclusion list.
Service Manager - Subscription templates sends e-mail in wrong language
We've been looking for a solution to why the subscription template configured as English (United States) sends out e-mails in Swedish.
It's pretty basic actually. If the locale variable is not set in Active Directory, the locale field on the user will be empty in Service Manager. Our guess is that SCSM then will base this upon the country variable, which in my case is Sweden. And since we want all e-mail correspondence in English we need to set the locale to English (United States) for all users.
To do this, we are creating a management pack with a powershell script scheduled to run once per day. For more information regarding this management pack and powershell script, please see the following links:
Powershell Script
Import-Module smlets ; Add-PSSnapIn SMCmdletSnapIn ;
#Delete the existing data from the CSV Clear-Content -Path "E:SMAdminCSVUsers.csv"
#retrieve all users from the CMDB and cycle through them
$users = (get-scsmclass Microsoft.AD.User$ | get-scsmobject)
foreach ($user in $users)
{
$UserName = $user.UserName #get the username, used to identify the person
$Domain = $user.Domain #get the domain, this is required for a CSV import
$ID = $user.ID #get the users guid, we will use this to create the ID for the settings object $setPref = 'Pref.' #used as a prefix for the localsetting object id
$setID = $setPref,$ID
$setID = [string]::join('',$setID) #combine the users guid and Pref. to make the id for localesettings
if ($user.City -like "Shanghai") {$timezone = 'China Standard Time'}
elseif ($user.City -like "Dhaka") {$timezone = 'Central Asia Standard Time'}
else {$timezone = 'W. Europe Standard Time'}
$locale = '1033' #setting the locale, in this case it's English (United States)
$data = $UserName, $Domain, $setID, $timezone, $locale #put it all into an array
[string]::join(',',$data) | ForEach-Object {Add-Content -Value $_ -Path "E:SMAdminCSVUsers.csv"}; #convert the array to a string and append to the csv
}
#once all users have been added to the csv, import it into the CMDB using the xml mapping file.
Import-SCSMInstance -DataFileName "E:SMAdminCSVUsers.csv" -FormatFileName "E:SMAdminCSVUserImport.xml"
#Remove any automatically created localization settings, the script has create new ones for everybody
get-scsmclass System.UserPreference.Localization$ | get-scsmobject -filter {DisplayName -notlike "%-%"} | remove-scsmobject -force
Remove-PSSnapIn SMCmdLetSnapIn;
Remove-Module smlets;
Management Pack
Configuration Manager Remote Control Disabled after install
After installing the Configuration Manager client on a Windows XP workstation. The client appears to install fine but the Configuration Manager Remote control service is stopped and the startup type is set to disabled. My ccmsetup.log says the install was successful and the client shows up in the configuration manager console.
To solve this issue, start by changing the following values in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control
Access Level 0 => 2
Allow Local Administrators to do Remote Control 0 => 1
Audible Signal 1 => 0
Enabled 0 => 1
Firewall Exception Profiles 0 => 15
Permission Required 1 => 0
PermittedViewers Administrators => blank
Finally, set the service Configuration Manager Remote Control to Automatic and start it.
I do not know why this happened, but I'm suspecting that it has something to do with the client not being assigned to a boundary group.
Failed to get client identity (80004005)
PXE keeps rebooting after Preparing network connections.
Errors in smsts.log:
reply has no message header marker
Failed to get client identity (80004005)
failed to request for client
Resolution: Set correct time and date in BIOS
SCCM Agent not working after OS deploy
The agent doesn't get the self signed certificate after os deployment.
Right after the "Setup Windows and ConfigMgr" step, add two "Run Command Lines" to set the registry values correctly. Here are the two commands to be run:
Finding duplicate systems in SCCM
Fire up SQL Management Studio and use som of the following queries:
Find duplicate MAC addresses
SELECT dbo.v_RA_System_MACAddresses.MAC_Addresses0, Count(dbo.v_R_System.Name0) AS SystemCount FROM dbo.v_R_System RIGHT OUTER JOIN dbo.v_RA_System_MACAddresses ON dbo.v_R_System.ResourceID = dbo.v_RA_System_MACAddresses.ResourceID GROUP BY dbo.v_RA_System_MACAddresses.MAC_Addresses0 ORDER BY SystemCount DESC
Find ResourceID for the duplicate MAC address
select * from dbo.v_RA_System_MACAddresses where MAC_Addresses0 = '00:00:00:00:00:00'
Find Name0 for the duplicate MAC addresses
select * from dbo.v_R_System where ResourceID = '12345678' OR resourceid = '12345678'
Find duplicate computer names
select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier, R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r full join SMS_R_System as s1 on s1.ResourceId = r.ResourceId full join SMS_R_System as s2 on s2.Name = s1.Name where s1.Name = s2.Name and s1.ResourceId != s2.ResourceId
Find duplicate HardwareID's
SELECT Name0, Hardware_ID0, Count(Hardware_ID0) AS SystemCount FROM dbo.v_R_System GROUP BY Hardware_ID0, Name0 ORDER BY SystemCount DESC
Windows XP bluescreens after OS deployment
Don't forget to include mass storage driver. You can get a driver pack that covers the most models on the link below.
Create a Driver Package including all the drivers from the link above, then create a Apply Driver Package step in your Windows XP task sequence selecting the newly created Driver Package.
SCCM 2012 Windows XP OSD installing to D:
I've been having issues with Windows XP being deployed to D:, and finally I've found the solution.
There's an error in the MDT task sequence step "Format and Partition Disk 5.x".
In the Options tab there's some conditions, and one condition is:
ImageOSVer equals 5.1 AND ImageOSVer equals 5.2. I will now tell you - THIS WILL NEVER HAPPEN ;)
Change this by adding an If-statement matching ANY of the listed conditions.
Now, the disk will get partitioned and formatted and the OS will end up at C:.
Out!
WFCRUN32 Error - Failed to set Event Logging
I got this error when deploying Citrix Online Plugin 12.1 and 12.3 on a freshly installed computer. I think it has something to do with User Account Control, but our group policy doesn't disable UAC before System Center tries to install the software.
Seems like adding the option DONOTSTARTCC=1 solves the problem though :)
CitrixOnlinePluginFull.exe /silent SERVER_LOCATION=http://WIServer DONOTSTARTCC=1
Have a nice weekend!
Object are not available and will not be edited
From time to time the SCCM console crashed, leaving objects locked from editing. If you don't have time to wait for an automatic unlock, do the following:
- Start SQL Management Studio and connect to the CM database
- Run select * from SEDO_LockState where LockStateID='1' and copy the id that is locked
- Run delete from SEDO_LockState where id='ID_FROM_ABOVE_SELECT'
Out!
Deployment not working on new Distribution Point
Been having trouble getting PXE deployment working on a new DP.
Looking in C:\SMS_DP$\sms\logs\SMSPXE.log I found:
Warning: Matching Processor Architecture Boot Image (0) not found
The solution is to make sure you to have both x64 and x86 images deployed even if you aren’t going to use both of them.
For both of your boot images, ensure ’Deploy this boot image from the PXE service point’ is ticked and then make sure you ‘Distribute Content’ to your PXE enabled DPs.
SCCM Agents fails push installation
Since upgrading to System Center Configuration Manager Service Pack 1 the agents fails the push installation with the following error message:
Couldn't verify 'C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi' authenticode signature. Return code 0x800b0101 ccmsetup 2013-01-16 20:38:01 6960 (0x1B30)
InstallFromManifest failed 0x80004005 ccmsetup 2013-01-16 20:38:01 6960 (0x1B30)
CcmSetup failed with error code 0x80004005 ccmsetup 2013-01-16 20:38:01 1204 (0x04B4)
A hotfix has been released by Microsoft, you can find it here:
Cheers!
Inactive Configuration Manager Agents
Some of our clients are listed as Inactive in Configuration Manager. This is the cause and resolution for one particular client having issues with Windows Management Instrumentation (WMI) on Windows XP.
I found this in %windir%\ccmsetup\ccmsetup.log:
MSI: Setup was unable to create the WMI namespace CCM The error code is 80041002 ccmsetup 2012-12-12 17:10:36 2192 (0x0890)
MSI: Action 17:10:36: Rollback. Rolling back action: ccmsetup 2012-12-12 17:10:36 2192 (0x0890)
MSI: Warning 25101. Setup was unable to delete WMI namespace ccm\dcm The error code is 80041002 ccmsetup 2012-12-12 17:10:37 2192 (0x0890)
File C:\WINDOWS\ccmsetup\{F5EAB9A8-E852-429F-92BC-BB82712ACA9B}\client.msi installation failed. Error text: ExitCode: 1603 Action: CcmCreateWmiNamespaces. ErrorMessages: Setup was unable to create the WMI namespace CCM The error code is 80041002 ccmsetup 2012-12-12 17:12:31 2192 (0x0890)
This indicates that there is something wrong with WMI on the client. I tried to find a way to repair WMI on Windows XP and found a solution where you should delete %windir%\system32\wbem\repository and restarting the "Windows Management Instrumentation" service. DO NOT perform this step, it will make the computer very unstable. Instead run the following commands in a Command Prompt to rebuild the WMI components.
FOR /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
net stop /y winmgmt
FOR /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
net start winmgmt
It's also a good idea to use WMI Diag during troubleshooting, it can be found here: