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