I faced this issue a few months back, where I could not patch one of our servers. Whenever I tried, I will got this : Error :  Windows Update Standalone Installer Installer encountered an error :  0x80070005 Access is denied. Troubleshooting : Troubleshooting 101 - check the service. Turned out, Windows Update service could not be found in the server... Resolution : There are 2 easy ways to resolve this.... Method 01 : 1) Go to a working server. 2) launch REGEDIT. 3) export below Registry key. Registry key : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv 4) import to the target server 5) restart the server Method 02 :  1) Apply below Registry Keys to the server : [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv] "PreshutdownTimeout"=dword:036ee800 "DisplayName"="Windows Update" "ErrorControl"=dword:00000001 "ImagePath"=hex(2):25,00,73,0

Orait.. Let's talk about Enterprise Vault Outlook Plugin again... The project that I involved requires a few versions jump - from EV ver 9 to EV ver 12. The planning was to upgrade Plugin to version 12 first, followed by servers upgrade. According to EV Compatibility List ( https://www.veritas.com/support/en_US/article.000097605 ), the plugin will be supported if the server is either the same version(n), n-1 or n+1.  Now back to the issue. Due to version incompatibility between the plugin and the server, during my testing, there was an information box appeared whenever I opened my MS Outlook, as documented below. Issue : Received below error after upgrading EV Outlook Plugin from version 9 to version 12 (where the EV server was still at ver 9). This version of the Enterprise Vault Outlook Add-In is not compatible with the Enterprise Vault server version. Contact your Help Desk for details of how to resolve the issue. At the same time, the Enterprise Vault plugin

I was part of a project to upgrade Enterprise Vault system - my task was to ensure the Enterprise Vault Outlook plugin is properly deployed to Outlook clients. However, during my testing to install Enterprise Vault Outlook Plugin ver 12, I faced an issue as below : Location is not valid. Choose a different installation location.  No logs, just a warning.  Thererfore, I performed some troubleshoting, which leads to the resoluton. Issue :  Unable to install Enterprise Vault Outlook Plugin version 12 - error : Location is not valid. Choose a different installation location.  Troubleshooting  Normal EV Outlook plugin installation won’t produce any log. Therefore, for troubleshooting purpose (which then be used during automation), the installer executed with MSIEXEC command : msiexec /i "C:\temp\EVOutlookClient\Veritas Enterprise Vault Outlook Add-in (x86).msi" /qn /norestart /l* C:\temp\EV12Installation.log   Based on the log, these error (marked in ye

Okay, I seriously thought I already have this post uploaded in this blog, but it turned out I was wrong. I have kept this for a long time, and it helped me a numbers of times already so I reckon it will help others as well. IE Connections. There are a few settings we can configured in IE Connections Settings such as : Automatically detect settings  Use automatic configuration script  Use a proxy server  Bypass proxy server for local addresses  Use different proxy servers for different protocols  Proxy server exception.  For this post, I will list registry keys positions for each setting. Objective : Grey-Out / Not-Grey-Out Automatic Configuration Location : Hive : HKCU Key : Software\Policies\Microsoft\Internet Explorer\Control Panel\ Value Name : AutoConfig Value Type : DWORD Value Data : 0 Result : Not-Greyed-Out, settings for Automatically detect settings & Use automatic configuration script can be changed. Value Data : 1 Result : Greyed-Out, settings f

I implemented this a few years back, when I needed to eliminate any unneeded pop-up to my users. In this case, it was for Adobe Reader. Newly created profiles will have this automatically pop-up when they launched Adobe Reader  for the first time. Adobe Product Improvement Program - Help Improve the Adobe Reader Experience. The screen also can be triggered by going to Help | Improvement Program Options... These steps will help to disable the Improvement Program Options menu, and consequently suppress the pop-up. Note that it requires registry editing, so be extremely careful. Note that the steps mentioned are for Adobe Reader 11. If oy used different version, ensure your key path refers to correct version (SOFTWARE\Policies\Adobe\Acrobat Reader\11.0) Using GPP :   Launch GPMC , and go to target GPO.   Edit the policy, and navigate to Computer Configuration | Preference | Windows Settings | Registry , right click at Registry , hover to New and click

I love to move my Windows profile folders from common, Microsoft-preset folders to my desired folders. And occasionally, out of stupidity, I mistakenly deleted the active folders, rather than the previous folders, which resulting to below error : <Path> refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location. As always, it is not hard to resolve this issue. However, it involves registry changes, therefore do it cautiously.  Open regedit  navigate to HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer  There are 2 parts here :  Shell Folders User Shell Folders Shell Folders is designed to be used by Windows NT and earlier. It is necessary not to delete this folder.

A few weeks ago I went to AppSense training. It was very good, very informative and very intense - 5 days were not enough to be honest as it covers all 4 components of DesktopNow (AppSense Management Console, Performance Manager, Environment Manager, and Application Manager). So back to the topic - I received this error while trying to pool the policy : Failed to poll Now : Not enough server storage is available to process this command. A bit digging, I managed to find why it happened, and how to resolve it. According to Microsoft : "This issue may occur if the IRPStackSize registry entry on the server is set too low." Now, what is IRPStackSize ?  According to Microsoft :  The IRPStackSize parameter specifies the number of stack locations in I/O request packets (IRPs) that are used by Windows 2000 Server, by Windows Server 2003, and by Windows XP. You may have to increase this number for certain transports, for media access control (MAC) drivers, or for fi