Using WSUS like a Proxy cache for windows updates.
Long story short I want updates to be done exactly as if there was no WSUS server, I could'nt care less about managing what updates my users can download or not download. I just want only
1 copy of the updates to be downloaded to WSUS or some proxy so i don't have 1000's of users downloading the same file 1000's of time. I really don't want a system that I need to approve any updates or retain 100's of GB's on my server. but
if a user needs a obscure printer driver I don't want to keep it on the server just because one user might need it.
Any Ideas?
Hi,
Any update?
Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support
Similar Messages
-
Domain Group Policy changes causes clients to be unable to connect to WSUS for Windows Updates
Domain Controller is Windows Server 2008 R2 64-bit, Group Policy Management version 6.0.0.1. WSUS server is Windows Server 2008 Enterprise 32-bit, Update Services version 3.2.7600.226. Client machines are Windows 7, some are 64-bit and some are 32-bit.
Every time we make any changes to any of our Group Policies most of our clients stop getting their Windows Updates from the WSUS server within 2-3 days. This occurs when we add a new policy for a group of users, temporarily disable a policy or edit a policy.
Check of the WindowsUpdate.log on affected client machines shows:
2014-06-25 13:40:44:976 760 1610 PT WARNING: GetAuthorizationCookie failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2014-06-25 13:40:44:977 760 1610 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 PT WARNING: PopulateAuthCookies failed: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 PT WARNING: RefreshCookie failed: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 PT WARNING: RefreshPTState failed: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 PT WARNING: PTError: 0x80072ee2
2014-06-25 13:40:44:977 760 1610 Report WARNING: Reporter failed to upload events with hr = 80072ee2.
A further check of the log files shows:
2014-06-21 19:36:06:995 156 1b0c Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <proxy server name:8080> Bypass List used : <(null)> Auth Schemes used : <>
We do not use a proxy except for Internet connections. We configure IE with a pac file. This is set through Group Policy since we restrict user accounts from being able to set it.
The clients that are connecting to the WSUS server have these entries instead:
2014-06-24 09:12:16:779 992 270 Agent Setting download properties on call A20329BC-3467-4B7E-B9F4-6AC6ACBA23E1: priority=3, interactive=1, owner is system=0, proxy settings=1, proxy session id=2
I have a routine that will fix the problem but it is time-consuming and pulls me away from other things I should be doing:
Run registry files on client machine (WindowsUpdate and AU) This is not always necessary and is already set by Group Policy and the affected clients already have the registry settings. No idea why it is necessary to do but it the steps below don't always
work unless it is.
netstop bits and netstop wuauserv
ipconfig /flushdns
Delete qmgr*.* files from Downloader folder
Delete Software Distribution folder
Run from command prompt:
sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
netstart bits and netstart wuauserv
wuauclt /resetauthorization /detectnow
Run Windows Updates again from Control Panel
This routine always fixes the problem but I've found that I must do each step to guarantee success.
How or where is the proxy setting being changed for WSUS that we see in the WindowsUpdate logs and how do I prevent this from happening? It is also curious that it happens to most but not all of the client machines. When it does happen it's not always the
same client machines.You're right - the WSUS server is on the inside and does not need a proxy server. Tried running the netsh winhttp reset proxy command but was still not able to connect to the WSUS server. After running the netsh winhttp reset proxy command received response:
Current WinHTTP proxy setting: Direct access <no proxy server>.
Ran the command at 13:49 and then tried Windows Updates again. Here's snippet from the log file:
2014-06-27 13:49:56:889 548 f6c AU Triggering AU detection through DetectNow API
2014-06-27 13:49:56:890 548 f6c AU Triggering Online detection (interactive)
2014-06-27 13:49:56:890 548 4b8 AU #############
2014-06-27 13:49:56:890 548 4b8 AU ## START ## AU: Search for updates
2014-06-27 13:49:56:890 548 4b8 AU #########
2014-06-27 13:49:56:893 548 4b8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {9CE06AB2-E859-4B4D-8D1A-193AD89623C5}]
2014-06-27 13:49:56:893 548 1260 Agent *************
2014-06-27 13:49:56:893 548 1260 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-06-27 13:49:56:893 548 1260 Agent *********
2014-06-27 13:49:56:893 548 1260 Agent * Online = Yes; Ignore download priority = No
2014-06-27 13:49:56:893 548 1260 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-06-27 13:49:56:893 548 1260 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-06-27 13:49:56:893 548 1260 Agent * Search Scope = {Machine}
2014-06-27 13:49:56:893 548 1260 Setup Checking for agent SelfUpdate
2014-06-27 13:49:56:893 548 1260 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-06-27 13:49:56:894 548 1260 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-06-27 13:49:56:901 548 1260 Misc Microsoft signed: Yes
2014-06-27 13:49:56:927 548 1260 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-06-27 13:49:56:934 548 1260 Misc Microsoft signed: Yes
2014-06-27 13:49:56:936 548 1260 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-06-27 13:49:56:943 548 1260 Misc Microsoft signed: Yes
2014-06-27 13:49:56:956 548 1260 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-06-27 13:49:56:962 548 1260 Misc Microsoft signed: Yes
2014-06-27 13:49:56:974 548 1260 Setup Determining whether a new setup handler needs to be downloaded
2014-06-27 13:49:56:974 548 1260 Setup SelfUpdate handler is not found. It will be downloaded
2014-06-27 13:49:56:974 548 1260 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-06-27 13:49:56:976 548 1260 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-06-27 13:49:56:976 548 1260 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-06-27 13:49:56:989 548 1260 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-06-27 13:49:56:989 548 1260 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2014-06-27 13:49:57:007 548 1260 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2014-06-27 13:49:57:007 548 1260 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2014-06-27 13:49:57:165 548 1260 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-06-27 13:49:57:165 548 1260 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://(FQDN of WSUS server)/ClientWebService/client.asmx
2014-06-27 13:49:57:175 548 1260 PT WARNING: Cached cookie has expired or new PID is available
2014-06-27 13:49:57:175 548 1260 PT Initializing simple targeting cookie, clientId = 6be4a1ae-3313-4855-bdb1-57e3312f03ec, target group = AGENCIES, DNS name = dpk2.clear-rcic.rcc.org
2014-06-27 13:49:57:175 548 1260 PT Server URL =
http://(FQDN of WSUS server)/SimpleAuthWebService/SimpleAuth.asmx
2014-06-27 13:50:57:280 548 1260 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(proxy server):8080> Bypass List used : <(null)> Auth Schemes used : <>
2014-06-27 13:50:57:281 548 1260 PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2014-06-27 13:50:57:281 548 1260 PT + Caller provided proxy = No
2014-06-27 13:50:57:281 548 1260 PT + Proxy list used = webgate.rcc.org:8080
2014-06-27 13:50:57:281 548 1260 PT + Bypass list used = <NULL>
2014-06-27 13:50:57:281 548 1260 PT + Caller provided credentials = No
2014-06-27 13:50:57:281 548 1260 PT + Impersonate flags = 0
2014-06-27 13:50:57:281 548 1260 PT + Possible authorization schemes used =
2014-06-27 13:50:57:281 548 1260 PT WARNING: GetAuthorizationCookie failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2014-06-27 13:50:57:281 548 1260 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: PopulateAuthCookies failed: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: RefreshCookie failed: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: RefreshPTState failed: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: Sync of Updates: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
2014-06-27 13:50:57:281 548 1260 Agent * WARNING: Failed to synchronize, error = 0x80072EE2
2014-06-27 13:50:57:282 548 1260 Agent * WARNING: Exit code = 0x80072EE2
2014-06-27 13:50:57:282 548 1260 Agent *********
2014-06-27 13:50:57:282 548 1260 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-06-27 13:50:57:282 548 1260 Agent *************
2014-06-27 13:50:57:282 548 1260 Agent WARNING: WU client failed Searching for update with error 0x80072ee2
2014-06-27 13:50:57:302 548 e04 AU >>## RESUMED ## AU: Search for updates [CallId = {9CE06AB2-E859-4B4D-8D1A-193AD89623C5}]
2014-06-27 13:50:57:302 548 e04 AU # WARNING: Search callback failed, result = 0x80072EE2
2014-06-27 13:50:57:302 548 e04 AU # WARNING: Failed to find updates with error code 80072EE2
2014-06-27 13:50:57:302 548 e04 AU #########
2014-06-27 13:50:57:302 548 e04 AU ## END ## AU: Search for updates [CallId = {9CE06AB2-E859-4B4D-8D1A-193AD89623C5}]
2014-06-27 13:50:57:302 548 e04 AU #############
2014-06-27 13:50:57:303 548 e04 AU Successfully wrote event for AU health state:0
2014-06-27 13:50:57:303 548 e04 AU AU setting next detection timeout to 2014-06-27 22:50:57
2014-06-27 13:50:57:304 548 e04 AU Setting AU scheduled install time to 2014-06-28 05:00:00
2014-06-27 13:50:57:304 548 e04 AU Successfully wrote event for AU health state:0
2014-06-27 13:50:57:305 548 e04 AU Successfully wrote event for AU health state:0
2014-06-27 13:51:02:285 548 1260 Report REPORT EVENT: {BD25B39C-6570-454C-A046-AF3AF2DEBDD4} 2014-06-27 13:50:57:282-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2 AutomaticUpdates Failure Software
Synchronization Windows Update Client failed to detect with error 0x80072ee2.
2014-06-27 13:51:02:295 548 1260 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2014-06-27 13:51:02:295 548 1260 Report WER Report sent: 7.6.7600.256 0x80072ee2 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2014-06-27 13:51:02:295 548 1260 Report CWERReporter finishing event handling. (00000000)
2014-06-27 13:51:48:184 548 4b8 AU ########### AU: Uninitializing Automatic Updates ###########
2014-06-27 13:51:48:187 548 4b8 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80080008.
2014-06-27 13:51:48:187 548 4b8 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80080008.
2014-06-27 13:51:48:187 548 4b8 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80080008.
2014-06-27 13:51:48:187 548 4b8 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80080008.
2014-06-27 13:51:48:187 548 4b8 Report CWERReporter finishing event handling. (00000000)
2014-06-27 13:51:48:252 548 4b8 Service *********
2014-06-27 13:51:48:252 548 4b8 Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-06-27 13:51:48:252 548 4b8 Service *************
2014-06-27 13:51:53:002 548 160c Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0400) ===========
2014-06-27 13:51:53:002 548 160c Misc = Process: C:\Windows\system32\svchost.exe
2014-06-27 13:51:53:002 548 160c Misc = Module: c:\windows\system32\wuaueng.dll
Ran a batch file which resets the AU and WindowsUpdate registry keys and then runs the steps listed above:
regedit /s C:\WindowsUpdate.reg
regedit /s C:\AU.reg
net stop bits
net stop wuauserv
Ipconfig /flushdns
del C:\ProgramData\Microsoft\Network\Downloader\qmgr*.*
del /F /Q C:\Windows\SoftwareDistribution\*.*
sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
net start bits
net start wuauserv
wuauclt /resetauthorization /detectnow
After this runs, am able to connect to WSUS server for updates. I mentioned Group Policy changes because this only breaks after the Group Policy changes. It doesn't affect every client machine but most of them. Was wondering how the proxy gets reset from
none to the proxy server for Windows Updates? -
Where is Support for Windows Update issues for Windows Server?
Where is Support for Windows Update Issues for Windows Server?
Windows Update keeps prompting to install an important update, KB2871690 and continually fails with error code 0x800f922
I ran all the fixes I can find, it still fails.
I also tried the manual install, fails.
Microsoft used to provide no charge support for Windows Update issues. They additionally offer online fixes for other versions of windows, but not server, and I can't find a forum.
I also cannot ignore the update, it continually prompts.
I ran the windowsupdate.diagcab and it continually states it fixes Windows Update error 0x80070057, by resetting windows update data store. It further states it fixes Problems installing recent updates.
But it doesn't. I've run it 50 times, and it says the same thing every time.
So there is no support for windows update, and no support for windowsupdate.diagcab.
What's the deal?I've done the SFC/ SCANNOW and DISM
here is the cbs.log
What are we looking for?
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~BT\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360'. -
CDISMManager::put_ScratchDir
2013-12-04 19:48:19, Info DISM PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$Windows.~BT\sources" - CDISMManager::LoadLocalImageSession
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Failed to get and initialize the PE Provider. Continuing by assuming
that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM.EXE:
2013-12-04 19:48:20, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2013-12-04 19:48:20, Info DISM DISM.EXE:
2013-12-04 19:48:20, Info DISM DISM.EXE: Host machine information: OS Version=6.2.9200, Running architecture=amd64, Number of processors=4
2013-12-04 19:48:20, Info DISM DISM.EXE: Dism.exe version: 6.2.9200.16384
2013-12-04 19:48:20, Info DISM DISM.EXE: Executing command line: X:\$Windows.~BT\sources\dism.exe /logpath:X:\$Windows.~BT\sources\Panther\cbs.log
/scratchdir:X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360 /image:X:\ /is-serviceable
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\FolderProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\FolderProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\WimProvider.dll -
CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Warning DISM DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\WimProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\VHDProvider.dll -
CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Warning DISM DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\VHDProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\ImagingProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Warning DISM DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\ImagingProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\CompatProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\CompatProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:20, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2013-12-04 19:48:20, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2013-12-04 19:48:20, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
2013-12-04 19:48:20, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
2013-12-04 19:48:20, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
2013-12-04 19:48:20, Warning DISM DISM.EXE: Failed to load WimManager. Try running from the Deployment Tools Command Prompt. If the issue persists, ensure that wimgapi.dll
and wimserv.exe are up to date.
2013-12-04 19:48:20, Warning DISM DISM.EXE: Failed to add any commands.
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 physical location path: X:\ - CDISMManager::CreateImageSession
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 Copying DISM from "X:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2013-12-04 19:48:20, Info DISM DISM Manager: PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD"
- CDISMManager::LoadRemoteImageSession
2013-12-04 19:48:20, Info DISM DISM Image Session: PID=1644 TID=1656 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:20, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:20, Info DISM DISM OS Provider: PID=1644 TID=1656 Defaulting SystemPath to X:\ - CDISMOSServiceManager::Final_OnConnect
2013-12-04 19:48:20, Info DISM DISM OS Provider: PID=1644 TID=1656 Defaulting Windows folder to X:\Windows - CDISMOSServiceManager::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Failed to get and initialize the PE Provider. Continuing by assuming
that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Manager: PID=1612 TID=1616 Image session successfully loaded from the temporary location: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD
- CDISMManager::CreateImageSession
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Getting Provider OSServices - CDISMProviderStore::GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM OS Provider: PID=1644 TID=1656 Setting SystemPath to X:\ - CDISMOSServiceManager::SetSystemPath
2013-12-04 19:48:22, Info DISM DISM.EXE: Target image information: OS Version=6.2.9200.16384, Image architecture=amd64
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Getting the collection of providers from an image provider store type. -
CDISMProviderStore::GetProviderCollection
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM OS Provider: PID=1644 TID=1656 Get the registry path to the SOFTWARE hive located at X:\Windows\system32\config\SOFTWARE
and determine if it is loaded. - CDISMOSServiceManager::DetermineBootDrive
2013-12-04 19:48:22, Info DISM DISM Driver Manager: PID=1644 TID=1656 Further logs for driver related operations can be found in the target operating
system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Warning DISM DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll.
- CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered. Attempting to initialize
the provider. - CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
- CDISMProviderStore::Internal_LoadProvider
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Current image session is [OFFLINE] - CTransmogManager::GetMode
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Determined WinDir path = [X:\Windows] - CTransmogManager::GetWinDirPath
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 GetProductType: ProductType = [ServerNT] - CTransmogManager::GetProductType
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Product Type: [ServerNT] - CTransmogManager::Initialize
2013-12-04 19:48:22, Info DISM DISM Transmog Provider: PID=1644 TID=1656 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
2013-12-04 19:48:22, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager.
2013-12-04 19:48:22, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2013-12-04 19:48:22, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1672 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2013-12-04 19:48:22, Info DISM DISM Provider Store: PID=1644 TID=1672 Provider has previously been initialized. Returning the existing instance.
- CDISMProviderStore::Internal_GetProvider
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1672 Processing the top level command token(is-serviceable). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1672 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2013-12-04 19:48:22, Info DISM DISM Package Manager: PID=1644 TID=1672 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Found the OSServices. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Found the OSServices. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Found the PE Provider. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Package Manager: PID=1644 TID=1672 Finalizing CBS core. - CDISMPackageManager::Finalize
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:23, Info DISM DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM OS Provider: PID=1644 TID=1672 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2013-12-04 19:48:24, Info DISM DISM.EXE:
2013-12-04 19:48:24, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2013-12-04 19:48:24, Info DISM DISM.EXE:
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Found the OSServices. Waiting to finalize it until all other providers
are unloaded. - CDISMProviderStore::Final_OnDisconnect
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2013-12-04 19:48:24, Info DISM DISM Provider Store: PID=1612 TID=1616 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider -
Using CUPC7/CUPC8.6 and Jabber for windows...unable to access voicemail.
Using CUPC7/CUPC8.6 and Jabber for windows...unable to access voicemail.
Setup includes CUCM9.0, Unity Connection 9.0, Presence 9.0....
steps taken to configure(and results acheived)
1-users created locally on CUCM and Enabled for IM and Presence.
2-able to login to clients (CUPS7/8.6 and Jabber) but getting error Voicemail Error. The server has rejected the provided credentials. [1903]
in order to verify there is nothing wrong with the credentials...i checked on unity and i am sure it's the PIN(12345) i need to use .
Can Anyone help me out here...Thanks in advance.It's not looking for your PIN - that is only used over DTMF-based interactions - it's looking for your CUC password. If the mailbox is synced from LDAP and you have LDAP Auth enabled on CUC, then this would be your AD password. If it's synced over AXL, not synced at all, or LDAP synced but without Auth, then there will be an alphanumeric password field on the mailbox under Edit > Change Passwords.
Please remember to rate helpful responses and identify helpful or correct answers. -
I have to use microsoft office 2007 and 2003 for windows and I'm using a macbook pro, How i can get the on mac?
You can either use Office for Mac 2011 or use Boot Camp to run Windows or use a VM, such as Parallels Desktop to run Windows. Running Windows, you'd be able to use MS Office for Windows.
Clinton -
How to remove "Ads by Media Player" using Chrome? Online solutions are for Windows
How to remove "Ads by Media Player" using Chrome? Online solutions are for Windows.
Having relentless pop up ads which open new browser windows. Searched all over for a Mac solution and can't seem to find one. Help please!?http://www.adwaremedic.com/index.php
(Read the whole page to learn about adware!) -
How To convert mp4 to mp3 using itunes 11.1.3.8 for windows
How To convert mp4 to mp3 using itunes 11.1.3.8 for windows
pgyan wrote:
How To convert mp4 to mp3 using itunes 11.1.3.8 for windows
The normal situation would be wanting to convert .m4a (AAC or Apple Lossless) to .mp3 as these are both music file formats. The extension .mp4 is normally for a video file and iTunes itself will only convert music files from one format to another.
For details on how to convert between music formats see http://support.apple.com/kb/ht1550
If you want to convert the audio track of an .mp4 video to a .mp3 file then you are going to need to use a different utility. -
Service account for Windows Update sync
Hi all,
I would like to know if it's possible to change service account used by WSUS 2008R2 SP1 to sync with Windows Update servers, and if so how.
Thanks. Have a good day.
FXEHi,
Do you want to use the different account for the WSUS management? Is so, that account must be a member of either the WSUS Administrators or the local Administrators security
groups on the server on which WSUS is installed in order to use the WSUS console.
The related KB:
Step 4: Configure and Synchronize WSUS
http://technet.microsoft.com/en-us/library/cc708455(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Updated URLs for Windows Update?
Greetings,
I'm locking down a thin client that will only have access to a few sites. We would also like to allow access to Windows Update. I've searched through Technet and other sites and they all seem to suggest allowing the following sites; even though some seem
to point to legacy systems. Is it still recommended to allow all of the following URLs? I haven't seen any recent KBs or posts to state otherwise. This is for a Windows 7 Professional solution:
windowsupdate.microsoft.com
*.windowsupdate.microsoft.com
*.windowsupdate.microsoft.com
*.update.microsoft.com
*.update.microsoft.com
*.windowsupdate.com
download.windowsupdate.com
download.microsoft.com
*.download.windowsupdate.com
wustat.windows.com
ntservicepack.microsoft.comHi,
As far as I know, If you block Windows update web site like Windowsupdate.microsoft.com, update.microsoft.com, Windowsupdate.com. You may encounter windows update check problem. That's to say, system won't find system important updates any more.
Roger Lu
TechNet Community Support -
I cannot get Icloud for windows update 4.0.2 to install on my Win 8.1 PC
I cannot get Icloud for windows update 4.0.2 to install on my Win 8.1 Pro PC its an AMD 64 bit processor.
I get a message that saysI cannot get Icloud for windows update 4.0.2 to install on my Win 8.1 Pro PC
I get the update notification and authorize its installation and it try's but fails.
I have down loaded the update and tried installation manually but it doesn't work.
I get the following message after it fails:
Errors occurred while installing the updates. If the problem persists, choose Tools > Dowmnload only and try installing manually.
I have tried this many times to no availI have been getting the same message for a few days now. Apple must have an a bug in this update
-
Microsoft releases fix for Windows Update corruption errors
See ZDnet article Microsoft releases fix for Windows Update corruption errors found @
http://www.zdnet.com/microsoft-releases-fix-for-windows-update-corruption-errors-7000026582/
The Microsoft KB article is found @
http://support.microsoft.com/kb/947821
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”Hi Rick,
Really thanks for your sharing.
This will definitly help others in this forum.
Kate Li
TechNet Community Support -
i wan't update using itunes, i want to make update using my phone, but when check for an update using software update in setting message appear " can't check for update....."?
Reboot the device and see if the error happens again. Updating through iTunes is usually optimal, but the file size differs via Software Update on the device and iTunes (50MB vs ~800MB)
-
WSUS + BITS Versions + Peer Caching + BranchCache + Windows Editions = HEADACHE!
We have a WSUS server in the main office (Windows Server 2008 R2 Standard).
We have a branch office with Windows 7 Professional clients and Windows Server 2008 R2 Standard and Enterprise servers, which means these computers are using BITS 4.0 (http://msdn.microsoft.com/en-us/library/bb968799(VS.85).aspx).
To save on disk space, we prefer not to set up a WSUS downstream replica server in the branch office if we can use BITS 4.0 with BranchCache.
Researching WSUS and BITS Versions and Peer Caching and BranchCache and Windows Editions has been confusing. Some questions…
These pages in the BITS section of MSDN all say: “Starting with Windows 7, the BITS 3.0 peer caching model is deprecated. If BITS 4.0 is installed, the BITS 3.0 peer caching model is unavailable.” However, these pages also say: “BITS (4.0) uses
the Windows BranchCache for peer caching,” and “Starting with Background Intelligent Transfer Service (BITS) 4.0, the BITS service was extended to allow subnet-level peer caching for downloaded URL data by using Windows BranchCache.”
http://msdn.microsoft.com/en-us/library/aa362708(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/aa964314(v=vs.85).aspx
http://msdn.microsoft.com/en-us/library/aa964240(v=vs.85).aspx
And this page says: “(BITS 4.0 New Feature) Peer caching now uses Windows BranchCache. This new peer caching model replaces the model used for BITS version 3.0.”
http://msdn.microsoft.com/en-us/library/aa363167(VS.85).aspx
Okay, fine. BITS 3.0 peer caching is unavailable for Win7/2008 R2, but BITS 4.0 “peer caching” does work by using BranchCache. Got it. So, do we understand correctly that the various “peer caching” group policy settings under Computer Configuration – Policies
– Administrative Templates – Network – Background Intelligent Transfer Service have
no effect at all for BITS 4.0 clients?
http://msdn.microsoft.com/en-us/library/aa362844(v=vs.85).aspx
Next, the link at the end of this paragraph says: “Windows BranchCache must be enabled on the client through a group policy or local configuration settings.” Okay, fine. We followed the instructions at the second link to enable BranchCache for our
Windows 7 clients. Interestingly, the description in the Turn on BranchCache group policy setting (under Computer Configuration – Policies – Administrative Templates – Network – BranchCache) says: “For this policy setting to take effect, you must install
the BranchCache feature on the client computer.” However, it seems that the BranchCache feature is
already installed by default (although not enabled) on Windows 7, because there’s no option to add BranchCache in Control Panel – Programs and Features – Turn Windows features on or off, and there’s already a BranchCache service on
Windows 7. So, does this statement actually not apply to Windows 7 (and only Windows Server 2008 R2)?
http://msdn.microsoft.com/en-us/library/aa964314(v=vs.85).aspx
http://technet.microsoft.com/en-us/library/dd637820.aspx
Next, the link below says: “The Windows BranchCache feature is an optional component that must be installed on the server,” and “The server must also enable the Windows BranchCache feature though group policy.” Okay, fine. We followed the
instructions at the second link to enable it for our Windows Server 2008 R2 servers. However, we would like one of our servers in the branch office to be the “Hosted Cache” server, and the remaining Win7/2008 R2 computers to just be “clients” that use the
Hosted Cache server (for the WSUS updates). So, in this case, does only the
Configuring a Web server or a BITS application server to use BranchCache section at this link apply to our Hosted Cache server, meaning no other steps are necessary beyond just installing the BranchCache feature? Or, do we have to go through the
Configuring a file server to use BranchCache section?
Likewise, does the Computer Configuration – Policies - Administrative Templates – Network - Lanman Server - Hash Publication for BranchCache group policy setting apply to us if we’re just looking to use BranchCache for WSUS updates and nothing else?
http://msdn.microsoft.com/en-us/library/aa964314(v=vs.85).aspx
http://technet.microsoft.com/en-us/library/dd637785.aspx
In doing more research I believe that, for Hosted Cache mode, the BranchCache feature must be installed on
both the WSUS server at the main site and on a server at the branch office. Is this correct?
Next, we want to configure the BranchCache Hosted Cache mode group policy setting. However, this setting says: “This address must match the Fully Qualified Domain Name (FQDN) of the server specified in the certificate for the BranchCache server's certificate,”
and “the certificate root for the BranchCache server's certificate must be in the client computer's trusted root store.” Since our BranchCache clients will only be using BITS for WSUS updates (via HTTP), is it still necessary to install a certificate
on the Hosted Cache server? (If Yes, that's too bad, because it really complicates BranchCache deployments, especially when all of the computers are within your Active Directory domain).
Next, there’s the Configure BranchCache for network files group policy setting. Since this setting uses SMB, we’re assuming this does not apply to BranchCache used by BITS clients, and so we don't need to configure it. Is this correct?
So, in Summary: We just want to use BITS with BranchCache for the computers in our branch office to access WSUS updates on a local server that’s acting as a BranchCache Hosted Cache server. And we’d prefer not to have to deal with certificates to make this
happen, if possible.
Sorry for the long post, but there’s just no clear, one-stop place that informs us how to configure all of this.
Oh, and is all of the above completely irrelevant
for us since this TechNet page says BranchCache requires the
Enterprise Editions of Windows 7 and Windows Server 2008 R2? I sure hope not… :o)
http://social.technet.microsoft.com/wiki/contents/articles/2342.branchcache-settings-for-windows-server-2008-r2-windows-7-enterprise-and-windows-7-ultimate.aspx
-Taylorbox
NOTE: I’ve already read these posts:
http://www.windowsnetworking.com/articles-tutorials/windows-7/Introduction-BranchCache-Part1.html
http://www.windowsnetworking.com/articles-tutorials/windows-7/Deploying-Hosted-Mode-BranchCache-Server-Part2.html
http://www.windowsnetworking.com/articles-tutorials/windows-7/Deploying-Hosted-Mode-BranchCache-Server-Part3.htmlFirst, I'm curious as to why you think that a BranchCache server would consume any less disk space than a WSUS replica server?
Because whereas our WSUS server stores all approved updates long-term, the BranchCache server would only store the updates needed for the branch office's computers, and
short-term.
Hmm.. this is not a benefit of branch-cache, it's merely a manifestation of an improperly maintained WSUS server.
The WSUS has over 100GB of updates.
Which is about TEN TIMES what should be held on a well-maintained WSUS server. :-)
The BranchCache server should use less than 5GB since it would keep only the most recent updates
Thus, BranchCache would contain about 50% IN CACHE of what a WSUS Replica Server would contain ON DISK.
This TechNet page says: "BITS uses the following Group Policies to enable and configure the peer caching," but then it says: "BITS 4.0: The BITS 3.0 Group Policies are deprecated.
Yeah, I did a double-take first time I saw that too... what it means is that those settings, originally used in BITS 3.0 have been deprecated, and now, with BITS 4.0 and BrancheCache you need to use the BITS 4.0 settings.
BrancheCache functionality is only available in the Enterprise and Ultimate editions of Windows 7.
A hosted cache server must be Enterprise or DataCenter editions; the functionality is not available in Standard Edition.
Evidently for Windows 8 Professional, BranchCache
is available for BITS (not SMB), but that's not true for Windows 7 Professional
This is a manifestation of the change in SKUs availabe in those two products. There is no Windows 8 Ultimate, only Professional and Enterprise, and there's no longer an Enterprise Edition of the Server OS.
In this case, when Microsoft removed the BITS 3.0 peer caching functionality with BITS 4.0 and replaced it with BranchCache, they effectively required you to use the Enterprise editions of Win7/2008 R2
Yes. BranchCache is a feature designed for Enterprise-scale organizations with Remote offices. The presumption, and a reasonable one at that, is that such organizations have volume licensing, and with volume licensing, desktops will be installed with Enterprise
Edition.
The requirement of WS2008R2 Enterprise Edition is a bit more onerous, but it's nothing new. Microsoft has always made notable feature distinctions between Standard and Enterprise Editions.
What's really significant now, though, is that Windows Server 2012 does not have an "Enterprise Edition". There's Standard Edition and Datacenter Edition, and ALL features are in BOTH editions ... so something to consider here if I've not yet convinced you
that the simplicity of a replica WSUS server is a better choice than the complexity of implementing BranchCache -- consider deploying WS2012 instead of WS2008R2.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
My MVP Profile:
http://mvp.support.microsoft.com/profile/Lawrence.Garvin
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
How to configure a proxy server for Windows Azure Tools in Visual Studio 2013
Hi Visual Studio/Azure Tools team
I would like to use the Windows Azure tools in Visual Studio 2013 to manage my Azure Web sites (Server Explorer -> Windows Azure -> Web Sites) from within my corporate network which is secured using a proxy server. Unfortunately, I am not able to use
the Windows Azure tools since the required HTTPS connection to windows azure is not going through the default configured proxy. Instead, Visual Studio tries directly to connect to port 443 which is blocked by our corporate firewall (and yes: there is no way
around using our proxy server). Other visual studio features like NuGet, updates, etc. work fine and use the configured proxy server.
So my question: How can I configure visual studio respective its Azure tools to use a proxy server instead of a direct connection? I already tried configuring the proxy server within the file devenv.exe.config but this doesn't show any effect for Windows Azure
tools.
Regards
tschaenaAs we have very similar problems I consider the found solution a work arround an existing problem which will not work if corporate FW policy does not allow such changes.
In my mind, any tools in charge of dealing with some sort of FW protocols should deliver the following information, should make it absolute clear how to setup that the request packages are setup rigth at the first time.
a) proxy server
b) proxy port
c) proxy user
d) proxy users-password
e) proxy.auth.Preference="BASIC"
And for moste tools (including Visual Studio and AZUR Tools) it is absolut unclear
a) how to setup that on a per tools basis
b) OR who inherits this information from whom i.e. use the same as IE does, what if we use FireFox or any other browsers?
I understand that developers requested to cure such problem areas will often have difficulty to gain all required elemenst used to realy test the solution.
But I can tell you: I loos more time figthing down the FW setups for my clients. WHat I do at home in a sniff, takes ages to be realised by all the various clients on the market where each has to deliver the same sort of information but actually does not,
or has it just somewhere, but not in the vicinity of the demanding user.
Good examples i.e. NetBeans IDE where the Option Menu shows very clearly what information is required to pass through a FW/Proxy; but even there, the hint to start with a BASIC authentication schema is not part of this OPTION menu and must be added a JAVA
environment value. But at least, it works.
Sepp -
How to add mSata SSD as HDD cache (for Windows 8)?
Hi,
I have T430 with HDD and Windows 8, 64. I have installed a new 32 GB mSata SSD, but I cannot figure out a way to set it up as a cache.
I am aware of the solution where ExpressCache needs to be installed but I have Windows 8 and the below link does not apply:
http://support.lenovo.com/en_US/downloads/detail.page?DocID=HT074404
I have also tried installing Interl Rapid Storage software. It does show my SSD but there is no option to "Accelerate". Googling points out that in BIOS I need to change SATA mode to RAID, but I only have Compatible and AHCI options there. Installing latest BIOS and lates Intel Rapid Storage drivers did not help.
Any other options I might be missing? Looks like it is either Lenovo publishes ExpressCache for Win 8 or adds IRS / RAID support in BIOS.
--Pavel
Solved!
Go to Solution.Ok, I have figured it out. Turns out that ExpressCache link for Windows 7 works for Windows 8 as well. After installing it I had to remove the volume from the SSD using disk manager and then run from the admin command prompt (can get there using Win+X key combo):
eccmd -partition
This command automatically found my SSD (again trick here is to make sure it is wiped clean first - not formatted and not partitioned).
Now I can see the status and effectiveness of caching via:
eccmd -info
Impressive - about 60% of read operations right now are from SSD. System is way more responsive and boots faster. You can see even that HDD lamp lights up less frequently. I definitely recommend adding an msata SSD if you have a HDD T430!
PS. ExpressCache.exe which I assume is GUI does not start though, I had to use the command line.
Maybe you are looking for
-
<script> window.resizeTo(350, 500); </script> that is what I did it works but is there anyway I can get rid of the menu bars and scroll for the windowresize?
-
HT201210 firmware software not up to date. could not update to 5.1
Downloaded 5.1 for my iphone 4 and got the message firmware was not compatible! Now what do I do? I was using 4.3 software and trying to upgrade. Only mention of firmware under settings is modem firmware for phone as 04.10.01.
-
Links from my RSS reader or Adium will no longer open in Firefox.
Today when trying to open links into Firefox it suddenly stopped working.
-
I've copied a .NET application from an older 2008 server running IIS 7.0.600.16386 to a newer 2008 R2 server running 7.5.7600.16385. The .NET framework version is 4.0.30319. I've setup an application pool and copied the wwwroot directory. I've che
-
hi I'm newbie to jsp and i want to know is there any familiar thing like a function? i developed some sites before in asp and php ...... and now i'm learning jsp.... what is the best thing in jsp to use if you have the same actions to do a lot of tim