syswow64 blog

This Blog will cover a native installation of Java 8 Update 66 and two App-v sequenced Java 6 Update 45 and Java 7 Update 45 Scenario: Virtualised Java 1.6.0.45 to connect to one java app Virtualised Java 1.7.0.45 to connect to another java app Latest version of Java locally installed on the PC Leave a comment if you would like me to write this blog in detail.

This Blog will cover a native installation of Java 8 Update 66 and two App-v sequenced Java 6 Update 45 and Java 7 Update 45 Scenario: Virtualised Java 1.6.0.45 to connect to one java app Virtualised Java 1.7.0.45 to connect to another java app Latest version of Java locally installed on the PC Leave a comment if you would like me to write this blog in detail.

SCCM 2012 R2 - Offline servicing error I attended a customer site in which their Windows 8 image was failing to OfflineService through ConfigMgr 2012 with the error 'Failed to install update with error code -2146498513' and 'ErrorCode = 2095' Log extract: Checking if update (1 of 13) with ID 16795476 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:35:56 PM 7876 (0x1EC4) dism.exe tool info: version=10.0.10586.0, architecture=9 SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:35:56 PM 7876 (0x1EC4) Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\740bf77e-4e9d-4817-81fb-ea9f3b35fd63\windows8-rt-kb2871389-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:36:51 PM 7876 (0x1EC4) Applying update with ID 16795476 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:36:51 PM 7876 (0x1EC4) dism.exe tool info: version=10.0.10586.0, architecture=9 S

SCCM 2012 R2 - Offline servicing error I attended a customer site in which their Windows 8 image was failing to OfflineService through ConfigMgr 2012 with the error 'Failed to install update with error code -2146498513' and 'ErrorCode = 2095' Log extract: Checking if update (1 of 13) with ID 16795476 needs to be applied on the image. 1 content binarie(s) are associated with the update. SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:35:56 PM 7876 (0x1EC4) dism.exe tool info: version=10.0.10586.0, architecture=9 SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:35:56 PM 7876 (0x1EC4) Applicability State = APPLICABLE, Update Binary = C:\ConfigMgr_OfflineImageServicing\740bf77e-4e9d-4817-81fb-ea9f3b35fd63\windows8-rt-kb2871389-x64.cab. SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:36:51 PM 7876 (0x1EC4) Applying update with ID 16795476 on image at index 1. SMS_OFFLINE_SERVICING_MANAGER 12/2/2015 2:36:51 PM 7876 (0x1EC4) dism.exe tool info: version=10.0.10586.0, archi

ConfigMgr 2012 Service Pack Upgrade (SCCM 2012 R2 SP1 upgrade) I was performing the initial Test Database command from the SMSSETUP\BIN\X64 directory of the installation media run the following command: (Setup.exe /testdbupgrade <database_name> ) Once the Pre-requistite check runs it references 'Unsupported ConfigMgr database version' and log states 'Failed to connect to SQL Server to verify site version'. If you search else where you may think this is a permissions based issue (definately check) but in my case this was not the case and i knew the database was supported. ===== INFO: Prerequisite Type & Server: SQL: ===== <<<RuleCategory: Database Upgrade Requirements>>> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>> INFO: CheckTestDBVersion start ... ERROR: Failed to connect to SQL Server to verify site version. Unsupported ConfigMgr database version;    Error;    For the site database upgr

ConfigMgr 2012 Service Pack Upgrade (SCCM 2012 R2 SP1 upgrade) I was performing the initial Test Database command from the SMSSETUP\BIN\X64 directory of the installation media run the following command: (Setup.exe /testdbupgrade <database_name> ) Once the Pre-requistite check runs it references 'Unsupported ConfigMgr database version' and log states 'Failed to connect to SQL Server to verify site version'. If you search else where you may think this is a permissions based issue (definately check) but in my case this was not the case and i knew the database was supported. ===== INFO: Prerequisite Type & Server: SQL: ===== <<<RuleCategory: Database Upgrade Requirements>>> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>> INFO: CheckTestDBVersion start ... ERROR: Failed to connect to SQL Server to verify site version. Unsupported ConfigMgr database version;    Error;    For the sit

SCCM 2012 SP2 Upgrade - Pending Restart If you attempt to run the SCCM 2012 SP2 upgrade, the prerequisite checker may inform you that the server is 'Pending a restart'. If after restarting the server you still get the same error message over and over, I have found a solution below: ConfigMgrPrereq.log extract <11-06-2015 13:00:36> ServerName001.domain.local;    Pending system restart;    Error;    Another program requires the server to be restarted before Setup can continue. Solution HKLM\Software\Microsoft\Server manager' 'CurrentRebootAttempts' should be set to 0 (and not 2) 'Actions' should be clear (Delete string value if present) For more SCCM tips and consulting, just leave a comment below!

SCCM 2012 SP2 Upgrade - Pending Restart If you attempt to run the SCCM 2012 SP2 upgrade, the prerequisite checker may inform you that the server is 'Pending a restart'. If after restarting the server you still get the same error message over and over, I have found a solution below: ConfigMgrPrereq.log extract <11-06-2015 13:00:36> ServerName001.domain.local;    Pending system restart;    Error;    Another program requires the server to be restarted before Setup can continue. Solution HKLM\Software\Microsoft\Server manager' 'CurrentRebootAttempts' should be set to 0 (and not 2) 'Actions' should be clear (Delete string value if present) For more SCCM tips and consulting, just leave a comment below!

Client-side logging By default, the client-side logging level is set to the value 1 in the registry. This means that Configuration Manager logs only Information, Warning, and Error messages. To enable verbose logging for those Configuration Manager logs that support it, do the following: 1. Open Registry Editor and find: HKLM\Software\Microsoft\CCM\Logging\@GLOBAL\LogLevel 2. Change the value of LogLevel from 1 to 0 (note that you will need to change the permissions for Administrators to have Full Control in order to change this value). 3. Restart the SMS Agent Host service. Client-side debug logging For even greater detail, you can enable debug logging. To enable debug logging for Configuration Manager logs, do the following: 1. Open Registry Editor and find: HKLM\Software\Microsoft\CC\Logging 2. Create a new key called DebugLogging. 3. Create a new value of type REG_SZ under this key and name it Enabled. 4. Set the Enabled value to True. 5. Restart the SMS Agent Host service.

Client-side logging By default, the client-side logging level is set to the value 1 in the registry. This means that Configuration Manager logs only Information, Warning, and Error messages. To enable verbose logging for those Configuration Manager logs that support it, do the following: 1. Open Registry Editor and find: HKLM\Software\Microsoft\CCM\Logging\@GLOBAL\LogLevel 2. Change the value of LogLevel from 1 to 0 (note that you will need to change the permissions for Administrators to have Full Control in order to change this value). 3. Restart the SMS Agent Host service. Client-side debug logging For even greater detail, you can enable debug logging. To enable debug logging for Configuration Manager logs, do the following: 1. Open Registry Editor and find: HKLM\Software\Microsoft\CC\Logging 2. Create a new key called DebugLogging. 3. Create a new value of type REG_SZ under this key and name it Enabled. 4. Set the Enabled value to True. 5. Restart the SMS Agent

Office 365 upgrade from Office 2007, 2010, 2013, 2016 Scenario : Estate contains Office Professional Plus and Standard installations of 2007, 2010, 2013 and 2016.  All version of Office suites must be removed leaving Visio and Project installation alone (i.e. 2007,2010, 2013, and 2016). The source files for Office 365 can be downloaded via the Click-To-Run URL here . This will download and extract two files (setup.exe and Configuration.xml). A download.xml and install.xml can be extrapolated from the accompanied configuration.xml; see below. “The Office 2016 Deployment Tool allows the administrator to customize and manage Office 2016 Click-to-Run deployments. This tool will help administrators to manage installations sources, product/language combinations, and deployment configuration options for Office Click-to-Run.” http://www.microsoft.com/en-us/download/details.aspx?id=36778 1.1        Download.xml The download.xml within the source files is kept as reference but is no longer requ