Wednesday, December 31, 2014

OS deployment fails (Failed to download policy )

Recently I have faced an issue with OS deployment. While OSD I got an error

While checking the smsts.log file I found the error in log file that was showing

BOM not found on policy reply

Failed to download policy {172A41CC-19A7-4BE3-91BC-0D979432CA10}/9 (Code 0x80004005).
I checked multiple things but nothing has worked.  Checked the package versions, scope IDs in application but everything was fine.
After that I searched the Policy in the SCCM database in table policyassignment and Policy
select * from policyassignment where policyid = '{172A41CC-19A7-4BE3-91BC-0D979432CA10}/9'
select * from policy where policyid = '{172A41CC-19A7-4BE3-91BC-0D979432CA10}/9'
after that I have deleted the policy which was showing as error in smsts.log file.
Delete from policyassignment where policyid = '{172A41CC-19A7-4BE3-91BC-0D979432CA10}/9'

Monday, April 21, 2014

Error while doing Prestage file on Sec Site/DP ExtractContent failed; 0x80040e09

I had an error while doing extract the prestage file on Sec Site

Above error was showing failed to execute the query to register content of package.
When I was checking everything was fine from DP site and as well as from Primary site.

Then again I checked the SQL permission on database, then found we have to grant the permission on service account in SQL server, which has been used for SQL server and Sec site/DP installation.

Then I provided the full permission on Service account then I was success

Saturday, February 22, 2014

The collation of the site database does not match the collation of the parent site's database

I had SQL error at the Prerequisite Check page regarding the required SQL Server Collation:

"The collation of the site database does not match the collation of the parent site's database.  All sites in a hierarchy must use the same database SCCM 2012"

Configuration Manager required that you configure your SQL Server instance and Configuration Manager Site database (if already present) to use the SQL_Latin1_General_CP1_CI_AScollation,

The server collation is specified during SQL Server installation.  So this means that you need to re-install the SQL server or rebuild your database.  The server collation acts as the default collation for all system databases that are installed with the instance of SQL Server, and also any newly created user databases.
It is highly recommend to do this only on a SQL which is not in use by any other application!
Navigate to your SQL setup folder or DVD where the setup.exe is located and execute the underneath command:

Sunday, February 16, 2014

List of errors code during the client installation

– The system cannot find the file specified.
5 – Access denied.
52 – You were not connected because a duplicate name exists on the network. Make sure there is not a duplicate name in DNS and that 2 machines don’t have the same IP in DNS.
53 – Unable to locate, cannot connect to admin$ – Computer Browser not started 
58 – The specified server cannot perform The requested operation
64 – The specified network name is no longer available. Source: Windows
67 – network name cannot be found.
86 – network password is not correct? Machine Name <> resolved name.
112 – Not enough disk space
120– Mobile client on the target machine has the same version, and ‘forced’ flag is not turned on. Not processing this CCR ,target machine already have cm client and no force install selected(always install).
1003 – Cannot complete this function.
1053 – The service did not respond to the start or control request in a timely fashion.
1068 – The dependency service or group failed to start
1130 – Not enough server storage is available to process this command. Source: Windows
1203 – The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator.
1208 – An extended error has occurred. Source: Windows
1305 – The revision level is unknown.
1396 – Logon Failure: The target account name is incorrect. (NBTSTAT -a reverse lookup, duplicate IP address)
1450 – Insufficient system resources exist to complete the requested service. Source: Windows
1789 – The trust relationship between this workstation and the primary domain failed.
2147749889 – Generic WMI failure (Broken WMI)
2147749890 – not found – Source: Windows Management (WMI) – try repair WMI
2147749904 – Invalid class – Source: Windows Management (WMI)
2147749908 – Initialization failure – Source: Windows Management (WMI)
2147942405 – Access is Denied (Firewall rule? / MacAfee-HIPS?)
2147944122 – The RPC server is unavailable. 

2148007941 – Server Execution Failed

Friday, January 31, 2014

Improve SCCM console performance

We can improve SCCM 2012 Console performance by using of SQL server, we will have to configure a setting known as Maximum Degree of Parallelism or MAXDOP for short. When SQL Server runs on a computer with more than one CPU, it detects the best degree of parallelism, the number of processors employed to run a single statement, for each parallel plan execution. This means that multiple queries may be executed. Setting the MAXDOP setting to the optimal setting can help improve performance by setting the limit to the number of physical processors.

We will use SQL to configure this value by using SQL Management Studio using the following steps:
1) In the object explorer, right click a server and select Properties.

 2)      Click the Advanced node.

      3) In the Max Degree of Parallelism box, select the maximum number of processors to use in parallel plan execution.
The default value of 0 uses all available processors. Set max degree of parallelism to 1 to suppress parallel plan generation. Set the value to a number greater than 1 to restrict the maximum number of processors used by a single parallel query execution. If a value greater than the number of available processors is specified, the actual number of available processors is used. If the computer has only one processor, the max degree of parallelism value is ignored.

Friday, January 3, 2014

Improve the performance of PXE boot

To improve the PXE boot we have to enable/add a registry value in DP where PXE is enabled,

From the distribution point (where you enabled PXE) complete the following

1.        Open regedit and locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP

2.        Add a QWORD value and call it RamDiskTFTPBlockSize

3.        Give it a Hexadecimal value of “4000″