Thursday, October 17, 2013

Enabling TPM on HP machines using SCCM 2012

To enable TPM on HP machines there is a tool from HP, Bios Configuration Utility, that modifies BIOS settings from Windows.To modify specified values to BIOS, first they can be exported using following command:
BiosConfigUtility.exe /getconfig:filename.txt

After verifying the exported file the values that we want to modify can be added in new file.
For example, to activate TPM on HP ProBook 6565b these value should be used:

English
OS Management of TPM
    Disable
    *Enable
Embedded Security Activation Policy
    F1 to Boot
    Allow user to reject
    *No prompts
Activate Embedded Security On Next Boot
    Disable
    *Enable
 

Next step is to execute the command to activate TPM on the specified model. Here it is important to note that to do this step there must be BIOS password enabled.
Here is the command:
biosconfigutility.exe /CurSetupPassword:"password" /setconfig:EnableTPM.REPSET

This command can be added in cmd file, and together with EnableTPM.txt can be added in SCCM package that latter can be executed in Task Sequence.


If you need to verify if TPM is enabled in the BIOS then this WMI command can be used:


SELECT * FROM Win32_Tpm where IsEnabled_InitialValue="False"

This command is considered for following WMI Namespace:
root\cimv2\Security\MicrosoftTpm

This command can be placed in Task Sequence:


 

Friday, October 4, 2013

Initializing the TPM Security hardware. Access denied.

Durring manual activation of Bitlocker in order to encrypt Operating system drive there is a message Access Denied.

To mention that TPM is already configured on the local machine. The reason why this message appears is that GPO is configured to write TPM Backup information in AD.


Here the question is that there is not enough permissions to write requested TPM information in AD.


If you follow this article and give enough permissions to SELF account then Bitlocker Encryption will continue.

Tuesday, August 6, 2013

Migrating a virtual machine from Windows XP to Windows 7 in VM Ware Workstation during SCCM 2007/2012 TS Migration

If there is Windows XP SP3 32-bit installed on VMWare Workstation with chosed Windows XP Professional platform then after migration to Windows 7 64-bit then Network card is not recognized in Windows 7.

In order to install Network Card in Windows XP SP3 which should be automatically recognized during migration to Windows 7 local VMWare vmx for the specified VMWare machine file should be modified.
After the line: ethernet0.addressType = "generated"

add the following line:

ethernet0.virtualDev = "e1000"

This line specify adding of Intell e1000 NIC.

After Windows XP booting you will be asked to install NIC drivers.

Here is the link from where Intel NC drivers can be downloaded:

http://www.intel.com/support/network/sb/cs-006120.htm

During the installation, instal just the drivers, not other components.


Monday, July 29, 2013

Migrate Regional Settings -Text Services and Input Languages using USMT 5.0



To migrate Text Services and Input Languages using USMT 5.0 from Windows XP to Windows 7 this specified setting should be configured in config.xml file:

<component displayname="Microsoft-Windows-Win32k-Settings-DL" migrate="no" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-win32k-settings-dl/microsoft-windows-win32k-settings-dl/settings"/>

Also I specified following settings:

<component displayname="Microsoft-Windows-International-TimeZones-DL" migrate="no" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-international-timezones-dl/microsoft-windows-international-timezones-dl/settings"/>

    <component displayname="Date, Time, Language and Region" migrate="no" ID="date_time_language_and_region">

      <component displayname="Regional Language Options" migrate="no" ID="date_time_language_and_region\regional_language_options">

        <component displayname="Microsoft-Windows-TextServicesFramework-Migration-DL" migrate="no" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-textservicesframework-migration-dl/microsoft-windows-textservicesframework-migration-dl/settings"/>

        <component displayname="Microsoft-Windows-MUI-Settings-DL" migrate="no" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-mui-settings-dl/microsoft-windows-mui-settings-dl/settings"/>

        <component displayname="Microsoft-Windows-International-Core-DL" migrate="no" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-international-core-dl/microsoft-windows-international-core-dl/settings"/>

      </component>

To get prepared config.xml create firs with /genconfig and /targetwindows7 switches.

Monday, February 4, 2013

Task Sequence failed with the error code (0×80070002); Network access account credentials not supplied

Task Sequence on SCCM 2012 has failed with following error:

Task Sequence failed with the error code (0×80070002)



Smsts.log file from target machine showed following:

Network access account credentials not supplied



After that Task Sequence failed:


To resolve this issue, Network Access Acount has to be configured in SCCM 2012.

Click on Sites-> Right click on Distribution Point -> Click on Configure Site Components ->Software Distrubition.

 
 
Click on Network Access Account and specify account with natwork access location perimisions.
 
 
 



Friday, February 1, 2013

Task sequence execution failed with error code 80004005

Durring OS deployment SCCM 2007 Task Sequence can crash and on the target machine in the C:\SMSTSLog\smsts.log file there is a following line:
The step (HP QuickLaunch Buttons 1.0) must be running in full OS


Failed to run the action: HP QuickLaunch Buttons 1.0.
The request is not supported. (Error: 80070032; Source: Windows) TSManager 1/31/2013 8:02:24 PM 260 (0x0104)

                


This issue is result that the machine is still in Windows PE mode.
To run in Windows OS Full Mode, Restart Windows component in SCCM Task Sequence should be modified to "The currently installed default operating system".


Monday, January 7, 2013

Firefox Bookmarks and USMT 4.0

Firefox Bookmarks and profile migration using USMT 4.0 is supported.
In migapp.xml there is a section which support migration of Firefox  3.0.
To support migration of all version of Mozila Firefox the original migapp.xml  should be modified.

This line:

MigXmlHelper.DoesObjectExist("Registry","%HklmWowSoftware%\Mozilla\Mozilla Firefox 3.*\bin [PathToExe]")

should be replaced with this line:

MigXmlHelper.DoesObjectExist("Registry","%HklmWowSoftware%\Mozilla\*.*\bin [PathToExe]")