Skip to main content

Posts

Solved : The user profile failed to attach. The process cannot access the file becase it is being used by another process

Issue :  The user profile failed to attach. Please contact Support. Status : 0x0000000B, Message: Cannot open virtual disk Error Code: 0x00000020, Message: The process cannot access the file becase it is being used by another process Solution :  Connect to Azure: # Connect-AzAccount Select the subscription of the target storage account: # Select-AzSubscription -subscriptionid "SubscriptionID" Create context for the target storage account: # $Context = New-AzStorageContext -StorageAccountName "StorageAccountName" -StorageAccountKey "StorageAccessKey" Get Current open files Get-AzStorageFileHandle -Context $Context -ShareName "WVDUserProfilesShareName" -Recursive | Sort-Object ClientIP,OpenTime Close an open handle: # Close-AzStorageFileHandle -Context $Context -ShareName " WVDUserProfilesShareName " -Path 'New folder/Profile_Username. vhd ' -CloseAll
Recent posts

Solved | SendGrid SSL CERTIFICATE_VERIFY_FAILED certificate verify failed | self signed certificate in certificate chain

Error :   PS C:\Ashish> & "C:/Program Files/Python39/python.exe" c:/Folder/SendEmail.py Traceback (most recent call last):   File "C:\Program Files\Python39\lib\urllib\request.py", line 1346, in do_open     h.request(req.get_method(), req.selector, req.data, headers,   File "C:\Program Files\Python39\lib\http\client.py", line 1279, in request     self._send_request(method, url, body, headers, encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1325, in _send_request     self.endheaders(body, encode_chunked=encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1274, in endheaders     self._send_output(message_body, encode_chunked=encode_chunked)   File "C:\Program Files\Python39\lib\http\client.py", line 1034, in _send_output     self.send(msg)   File "C:\Program Files\Python39\lib\http\client.py", line 974, in send     self.connect()   File "C:\Program Files\P

Automating Windows Updates using PowerShell

Scenario : Windows Server Operating Systems (2008 R2, 2012, 2012 R2, 2016) Issue : Managing the Windows Updates for multiple servers is a complex task. This can be simplified using PowerShell. Michal Gajda from Microsoft forum has done a wonderful job by creating custom PowerShell Module for Managing windows updates thru PowerShell. Link for the Module : https://goo.gl/qJHorX Description : The PSWindowsUpdate module allow you to manage Windows Update on your computer. Module contain set of function to check, download and install or remove update from local machine. Especially useful on machines in core edition like Windows Server 2008 R2 or later. Steps : Download : Download the ZIP from above link ( https://goo.gl/qJHorX ). Module can be installed manually by downloading Zip file and extract in two places : %USERPROFILE%\Documents\WindowsPowerShell\Modules %WINDIR%\System32\WindowsPowerShell\v1.0\Modules Importing the module PS > Import-Module PSWindowsUpdate Enable RemoteEx

Resolved | Windows Server 2008 R2 SP1 Update Fails

Issue: Windows Server 2008 R2 SP1 Installation fails Environment: Windows Server 2008 R2 Operating System OS Solution: 1) Open Windows Explorer and navigate to C:\Windows\Inf folder 2) Cut and Paste following files starting with name USB in another safe location: 3) Install the SP1 Update 4) After successful installation, place those files back. Comment if this solution works for you.

Fixed | WSUS 2016 | Error Code 0x8024401c | Windows 10 | Windows Server 2016

Scenario : Server : Windows WSUS Server 2016 Client : Windows 10, Windows Server 2016 Error Code :  0x8024401c on Windows 10 or Windows Server 2016 Solution : 1) Go to IIS Manager on WSUS Server 2) Goto Advance Settings of  WsusPool. 3) Make sure following settings are present/configured on the Pool, if not change it to below: Queue Length: 25000 Limit Interval (minutes): 15 "Service Unavailable" Response: TcpLevel Private Memory Limit (KB): 0 4) Make sure, the WSUS Entry in the Registry is having fully qualified domain name of WSUS Server. 5) Stop the IIS 6) Edit the web.config located at following location on WSUS Server : C:\Program Files\Update Services\WebServices\ClientWebService\web.config Replace <httpRuntime maxRequestLength="4096" /> with <httpRuntime maxRequestLength="204800" executionTimeout="7200"/> 7) Start the IIS 8) Retry updating clients. Done! Let me know if it has helped to y