Quest Workstation Updater 4.4.1

Transcription

1 Quest Workstation Updater Reference Guide

2 2010 Quest Software, Inc. ALL RIGHTS RESERVED. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc. The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA USA legal@quest.com Refer to our Web site for regional and international office information. TRADEMARKS Quest, Quest Software, the Quest Software logo, and Spotlight are trademarks and registered trademarks of Quest Software, Inc. Other trademarks and registered trademarks used in this guide are property of their respective owners. Quest Workstation Updater Reference Guide Updated - January 2010 Software Version

3 CONTENT About This Guide Joining Workgroups to a Target Domain Generating Mapping Files Drive Mapping File Shortcut Mapping File User Mapping File Troubleshooting the Profile Updater Removing a Novell Client Server Link Updater (LU.exe) and OLE Link Updater Resource Updating Monitor About Quest Software Contacting Quest Software Contacting Quest Support

4 Quest NDS Migrator 4

5 Workstation Updater Reference Guide About This Guide The purpose of this document is to serve as a reference guide for deploying and troubleshooting WorkStation Updater. This guide covers the following topics: Joining Workgroups to a Target Domain Generating Mapping Files Removing a Novell Client Server Link Updater (LU.exe) and OLE Link Updater Resource Updating Monitor Joining Workgroups to a Target Domain For the purpose of NDS Migrator, NETDOM.EXE is used to move computers from a workgroup to the target domain. On the console side, Netdom.exe must be installed and reachable via the system environment variable, PATH. Netdom.exe is not installed on Windows systems by default. To install Netdom.exe on a computer that is running Windows Server 2003, run the Suptools.msi program that is located in the Support\Tools folder on the Windows Server 2003 CD. On other operating systems, download and install the appropriate Support Tools package for that operating system from For more information on NETDOM.EXE, see the following Microsoft article titled "Netdom Overview" found at the following link: 3.mspx?mfr=true To join workgroups to a domain 1. Select Start Quest Software NDS Migrator. 5

6 Quest NDS Migrator 2. Select Tools Workstation Updater to launch the Workstation Updater Guide. Although not (visually) shown, the first three buttons (Specify Credentials Select Workstations Join Workstations to Domain) are used to capture values to place into the NETDOM.EXE command as switch values. The 'Specify Credentials and Join Workstations to Domain' have no bearing or connection to the 'Generate Mapping Files Update Workstation Resources nor Remove Novell Client' options. 3. Select the Specify Credentials button to capture the Local Computer's (that is still within the workgroup) and domain administrative accounts. This will make an administrative connection from the NDS Migrator computer to the WorkGrouped computer 4. Enter the Local Administrator Credentials and Domain User Credentials. 6

7 Workstation Updater Reference Guide 5. Select Specify Workstations button and specify the workstations. Click OK. 6. Select Join Workstation to Domain button and enter the target domain information. 7. Click Next. The workstations are joined to the target domain. The following shows a log file with a successful migration: 7

8 Quest NDS Migrator The following shows a log file when NETDOM.EXE errors (simple file sharing on): If the 'Organization Unit' is left blank, this will move the computer to the default Computers OU. If the 'Reboot workstations after 60 seconds if successful' is not checked, the computer will need to be manually restarted to complete the join. This may be for the scenario where updating needs to be done but the users still need to log into the workgroup. For this, as soon as the user (or administrator via script/3rd party tool) restarts the computer, it will default to the domain for login. Generating Mapping Files The Generate Mapping Files creates mapping files for the following three areas: Drive Mapping File Shortcut Mapping File User Mapping File Overall, the mapping files are generally used for either a search/find/replace action (OLE/Shortcut/Drive Mapping update) or a search/find/append action (User Profile). Before generating any mapping files, you must join a workstation to a target domain. 8

9 Workstation Updater Reference Guide To select mapping files From the Workstation Updater Guide dialog box, select Generate Mapping Files. Each mapping file is used for different areas of the tool. 9

10 Quest NDS Migrator Drive Mapping File The DriveMap.exe looks for persistent drive mappings and changes them to another value. A persistent drive mapping is set by selecting the 'Reconnect at logon' checkbox on the Map Network Drive dialog box. For more information on this setting, see the following Microsoft article titled "Drive letter" at the following link: true?. 10

11 Workstation Updater Reference Guide To perform the Drive Mappings update From the Select Mapping Files dialog box, select Drive Mapping File. A DriveMap.ini file is generated at the following (default) location: C:\Program Files\Quest Software\NDS Migrator\Tools\mapping\drivemap.ini The contents are taken from the 'Volume Mappings' tab of Quest NDS Migrator: If further link paths need to be entered, add them to this file prior to running the Drive Mappings update action. 11

12 Quest NDS Migrator The options are restricted to the location of the.ini file as the Drive Mappings are housed in the registry of the computer being updated: When the wizard completes, the WUPD.exe will attempt to copy the needed files and schedule a task on the remote computer (CS-MiG1-MOVEME1 for this example): where: Folder structure name is called:c:\questsoftware\ndsmigratorworkstationupdaterupd Files copied (for this action although others are copied):wupd.exe, DriveMap.exe, and Mapping\drivemap.in Log created:drivemapdate_time_stamp.log Scheduled Task Name: UPD_COMPUTERNAME_DATETIMESTAMP When the task is created from NDS Migrator, the task runs on the remote computer (CS-MIG1-MOVEME1 for this example) and the tool (WUPD.EXE) immediately adds the DriveMap.exe command to the RunOnce area of the registry for each user profile on the computer: 12

13 Workstation Updater Reference Guide When the user logs off and logs back in, the RunOnce value runs which calls the DriveMap.exe. For more information on the 'RunOnce' registry key, see the following Microsoft KB article titled 'A definition of the Run keys in the Windows XP registry': When triggered to run, the DriveMap.exe caches the drivemap.ini contents and parses the registry for a match. If a match is found, it checks the target path to be sure it exists. DriveMap.exe will only set the target value if it is reachable from the computer running the DriveMap.ini. Here is a sample log where the target path is not found: 13

14 Quest NDS Migrator If there is a failure to locate the target path, the tool has already removed the mapping so the end result is the mapping will be removed (and no update will have occurred), and a successful log (where the mapping is '\\cs-mig1-moveme\c$=\\cs-mig2k3srv01\address' and '\\cs-mig2k3srv01\address' is accessible from the 'cs-mig1-moveme1' computer. Shortcut Mapping File The Shortcut Updater (SU.exe) looks for *.LNK files and updates the target path. 14

15 Workstation Updater Reference Guide To perform shortcut mappings From the Select Mapping Files dialog box, select Shortcut Mapping File. A Shortcutmap.ini file is generated in the following (default) location: C:\Program Files\Quest Software\NDS Migrator\Tools\mapping\shortcutmap.ini. The Shortcut Updater (SU.exe), OLE Link Updater have the following options: Shortcut Full Path:' (this can be any local path (to the computer being updated) or a UNC path similar to '\\ServerName\ShareName' when a specific file path needs to be updated. Shortcut Mapping File:' is the path to where the shortcutmap.ini file is currently. If this file has been changed and moved, update it here. 'Recursive' means search from the 'Shortcut Full Path:' as a starting point and search any subfolders below it. For more information on creating shortcuts, see the following Microsoft article titled "How to Create a Shortcut on the Desktop": 15

16 Quest NDS Migrator The contents are taken from the 'Volume Mappings' tab of Quest NDS Migrator: If further link paths need to be entered, add them to this file prior to running the Shortcut Mappings update action. When the wizard completes, the WUPD.exe will attempt to copy the needed files and schedule a task on the remote computer (CS-MiG1-MOVEME1 for this example): 16 Where: Folder structure name is called:c:\questsoftware\ndsmigratorworkstationupdaterupd Files copied (for this action although others are copied):wupd.exe, SU.exe, and Mapping\shortcutmap.ini Log/HTML files created: ShortcutUpdater_Time_Stamp.LOG/ ShortcutUpdater_Time_Stamp.HTM

17 Workstation Updater Reference Guide Scheduled Task Name: UPD_COMPUTERNAME_DATETIMESTAMP The following shows the log file of the SU.exe run where it finds a link that was at '\\cs-mig1-moveme1\c$' and successfully changes to '\\CS-MiG2K3SRV01\Address':...and the before and after of the *.LNK update: 17

18 Quest NDS Migrator The 'Start in:' path is not updated by the SU.exe tool. The SU.exe looks for the shortcutmap.ini (caches the values) and does a search/find/replace on the volume specified. The SU.exe does a check to see if the target path is accessible. If it is not (using the credentials to launch the SU.exe), the logs will show error and the action will not continue: The SU.exe can be run from the command line. To use the SU.exe at the command prompt, run the following command at the command prompt to find all the appropriate switches: SU.exe /? 18

19 Workstation Updater Reference Guide User Mapping File User Mapping generates a file for updating user and group resources. The generated file is based on object mappings created during migration. The profile updater updates the user profile such that either: the source user and the domain user can both see the same desktop profile (share) create a new profile such that the new domain user has an exact copy of the source desktop profile (copy). The updater offers two options for updating local profiles: the 'shared' approach and the 'copy' approach. Both options have their advantages and disadvantages and it is at the discretion of the customer to decide which approach would be better suited to their environment. Profiles on Windows NT based operating systems are stored in two pieces; each piece must exist in order for the profile update to be successful. The two pieces are as follows: Registry entry for the local profile: The path to the registry key containing the profile information is: HKLM\Software\Microsoft\WindowsNT\CurrentVersion\ProfileList. A subkey exists under this key for each profile referenced on the Workstation/Server. The subkeys for each profile are named based on the Users SID. This key contains important information concerning the location of the second piece of the users profile - the profile directory. The value in the Profile key that determines the path to the profile directory is 'ProfileImagePath'. Profile Directory (ProfileImagePath): The profile directory contains all of the user's specific settings, documents, and so on. This directory is the heart of the user's profile and if it is lost, the user account will lose all settings and documents (and so on) that are stored in the profile.? Copy verses Update (Shared) - Determining Which Method to Use Determine which method to use depends upon the environment and the scenario. Use the following information to make the determination as it relates to the environment and the business need: For more information, see the following Microsoft TechNet article titled "Domain Migration Cookbook Chapter 3: Domain Restructure" which highlights some advantages and disadvantages for each method: There are two basic methods for making a profile available to the migrated user while, at the same time, allowing for a fallback route: Shared profiles: Make the same profile available to the user's original account and the new account. One copy of the profile is accessed and updated by both accounts. 19

20 Quest NDS Migrator Copied profiles: Copy the original profile from its current location under the key named after the user's original SID to a key named after the user's new SID. Each account is associated with its own separate copy of the profile. Updates to one are not reflected in the other. The following lists the advantages and disadvantages of sharing and copying profiles. ADVANTAGES OF SHARING PROFILES Updates to the profile (for instance, changes to My Documents, shortcuts, and so on) while logged onto one account are accessible when subsequently logged on to the other account. DISADVANTAGES OF SHARING PROFILES When moving between the old and new accounts, results are currently unpredictable. An example would be a new Windows 2000 account profile, perhaps containing group policy references, is used when falling back to a source account where different group policy (or no group policy) is deployed. Conserves disk space because only one copy of the profile is stored. Makes a utility available to enable profile sharing. ADVANTAGES OF COPYING PROFILES Behavior is more predictable, and because data is not shared between the profiles, there is no chance of "polluting" the profile of one account with data appropriate only for another account in a different domain and forest. DISADVANTAGES OF COPYING PROFILES There may be unpredictable "fallback" results with application deployment policy in the new domain. Even though the old account profile is not altered by destination account activity, applications deployed on the desktop by destination domain group policy may try, under certain circumstances, to uninstall themselves or do other unpredictable things. Storing two profiles consumes extra disk space. To perform user mapping 1. Select Select Mapping Files User Mapping File. A fmap.usr file is generated and is located (by default) in the following location (per computer selected in the 'Select Workstations' dialog box): C:\Program Files\Quest Software\NDS Migrator\Tools\mapping\COMPUTERNAME\map.usr. This file can be opened with NotePad.exe and is formatted the following: SourceComputer\Account(**)TargetDomain\Account(**)SourceSID(**)TargetS ID The match will be attempted from the CN value of the NDS object (found in the NDS Migrator database) to the samaccountname value (also found in the NDS Migrator database). 2. Select Update Workstation Resources Update/Copy Profiles. The updater.exe (the tool actually used to perform the update) uses the map.usr to carry out the profile update as described in the 'Copy Profiles Option' and Update (Shared) Profile Option above. If the SourceSID and/or TargetSID values are not accurate, this will cause failures to occur when copying/updating profiles and may result in a empty default profile for the domain user. 20

21 Workstation Updater Reference Guide Copy Profiles Option This option creates a physical copy of the source user account's profile and performs the following steps for each profile for which a match is found (a source profile exists on the computer that is being updated): The user's SID subkey is created under HKLM\Software\Microsoft\WindowsNT\ CurrentVersion\ProfileList. All values from the source user's profile are copied to the newly created profile key in the registry. The updater determines a suitable directory to house the new profile The 'ProfileImagePath' value of the new key is set to the previously determined directory name. The contents of the source profile are copied to the target profile. The security descriptor of the source directory is copied to the newly created directory, replacing the source user's SID with the target user's SID. The copied ntuser.dat is loaded as a hive in the registry and re-permissioned to insert the target account and remove the source account in the permissions where the source account is present. All other permissions on the hive are maintained. If the source user account logs on to the system while the profile is being copied, the copy of the ntuser.dat for the user is locked and cannot be copied. If this is the case, the source users Ntuser.dat is loaded as a hive in the registry under HKUsers\Source SID. The updater resolves this potential problem by dynamically creating an ntuser.dat for the target account from this hive in the registry. In this case, after the ntuser.dat has been created, it is loaded as a hive in the registry and re-permissioned to insert the target account and remove the source account in the permissions where the source account is present. All other permissions on the hive are maintained. Update (Shared) Profile Option The update profile approach 'shares' the source user profile to allow the target user account to use this profile. The update profile option performs the following steps for each profile for which a match is found (a source profile exists on the computer that is being updated): The user's SID sub key is created under HKLM\Software\Microsoft\WindowsNT\ CurrentVersion\ProfileList. All values from the source user's profile are copied to the newly created profile key in the registry. The updater determines if the source user account is logged in during the profile update. If the source user is not logged on to the system, the ntuser.dat is loaded as a hive in the registry and re-permissioned to insert the target account in the permissions where the source account is present. All other permissions on the hive are maintained. If the source user is logged on to the system, the ntuser.dat is currently loaded as a hive in the registry under HKUsers\Source SID and re-permissioned to insert the target account in the permissions where the source account is present. All other permissions on the hive are maintained. The profile directory is re-permissioned to mirror the source account's permissions with the target account. This is not a full re-permissioning as only the specific source/target match is re-permissioned. The 'file/folder permissions' option for the updater will re-permission the contents of this directory if necessary. 21

22 Quest NDS Migrator Troubleshooting the Profile Updater 1 After the profiles have been updated, the target user account should receive the source user account's profile when it logs on to the target domain for the first time. If the update job appears to be successful but the target user receives a default profile when logging on to the workstation, then one of the following may be the reason for the problem: The source account has not yet been migrated using Quest NDS Migrator. Cause: The updater.exe cannot find a match for the source account because it does not yet exist in the Quest NDS Migrator mapping files. Special care should be taken for a multiple console configuration with a shared database, as the mapping files at all consoles may not be up to date when performing the update. To ensure that the mapping files are always up to date in this type of environment, it is recommended to rebuild the mapping files prior to performing any update jobs. This can be accomplished by selecting 'Generate Mapping Files' from the main Workstation Updater Guide dialog box of NDS Migrator. Resolution: Migrate the source user account (or re-generate the mapping files if migrated from another console), delete the target default profile, and rerun the update job. The source account did not have a profile on the workstation. Cause: The updater cannot find a match for the source account. Resolution: Ensure that the source account has a profile on the workstation. The target user account profile existed on the workstation prior to the profile update. Cause: The updater, when enumerating the profiles, determined that the target user account profile already exists. The updater procedures DO NOT delete the profile that already exists for the target account. The updater will not report any errors in this scenario because none have occurred. The verbose updater.log file for this update job will show: "Profile for 'Target Account' already exists. Resolution: Delete the default target profile and rerun the update job.? The source profile is loaded in the registry. If this is the case, the source user will be logged off of the machine, however a hive for the user is still loaded under HKUsers\Users SID. This can be caused by the one of the following: Cause: The source user account is running a service that uses the profile when running. In this case, the service keeps the hive loaded in the registry. Resolution1: Reset any services using the source account to another account, delete the default target account profile, and rerun the update. the registry. Resolution2: Download and use the Microsoft 'User Profile Hive Cleanup Service' found at the following link: 1B286E6D E18-B E2F3582&displaylang=en Cause: If the workstation being updated is Window XP, an RDP connection to the workstation may not have been terminated. In this scenario, the RDP session will continue to run if the session was only disconnected The troubleshooting tips presented in this document have been tested in our environments with our system configurations. We cannot guarantee that these tips will work in all environments and with all system configurations

23 Workstation Updater Reference Guide Resolution: Terminate the RPD Session for the source user, delete the default target user profile, and rerun the update job. Cause: The source user account logged off and the hive failed to unload from the registry. In this case, the target user attempts to logon, however the loading of the NTUser.dat file fails as it is in use and locked in the registry. Resolution1: If this is the case, the following TechNet articles from Microsoft may be of some assistance: /technet/prodtechnol/windowsnetserver/proddocs/datacenter/c_profileunloadtimeout.asp Resolution2: Download and use the Microsoft 'User Profile Hive Cleanup Service' found at the following link: 1B286E6D E18-B E2F3582&displaylang=en The profile updater does not update Roaming Profiles. Removing a Novell Client The Workstation Updater does not use the same technique that "Control Panel -> Add/Remove Programs" uses. Instead, the following occurs: 1. A Quest Software uninstall agent NWRM.EXE is deployed to the client and scheduled. 2. When NWRM.EXE runs, it determines the Windows system directory. In the NetWare\Nwmigw2k subfolder of the Windows system folder, there is supposed to be a NetWare client utility SETUPW2K.EXE. NWRM runs the SETUPW2K.EXE six times as follows: System32\NetWare\Nwmigw2k\SETUPW2K.exe /u ms_nwspx System32\NetWare\Nwmigw2k\SETUPW2K.exe /u ms_nwnb System32\NetWare\Nwmigw2k\SETUPW2K.exe /u ms_nwipx System32\NetWare\Nwmigw2k\SETUPW2K.exe /u nw_wm System32\NetWare\Nwmigw2k\SETUPW2K.exe /u nw_ndps System32\NetWare\Nwmigw2k\SETUPW2K.exe /u nw_nwfs 3. Once complete, NWRM.EXE pauses for 30 seconds and then tries to reboot the computer. The NWRM agent creates a log file name NWRM.Log. If the uninstall fails, this log file may aid in determining why the uninstall failed on the said computer. Again, the above technique is not what the NetWare uninstall in Add/Remove Programs does. On my computer, the Add/Remove Programs uninstall uses NWSETUP.DLL. Novell TID documents the NWRM approach as an uninstall technique for removing NetWare Client off of Windows 2000 computers from a batch file. But, the disclaimer on the TID warns that: "This information is provided, as is. This is not a supported method of removing the Novell Client and therefore you should not attempt to open an incident to gain support for this document." It may not work reliably for later versions of NetWare clients or certain Windows operating systems. 23

24 Quest NDS Migrator Server Link Updater (LU.exe) and OLE Link Updater The Server Link Updater (LU.exe), OLE Link Updater goes into Office documents (see the User Guide for more information) and updates OLE links. Basically it does a search, find and replace action. To perform the Server Link Updater (LU.exe), OLE Link Update 1. Open NDS Migrator. 2. Select Tools Server Link Updater. 3. From the Server Link Updater dialog box, select Generate. A Linkmap.ini is generated at the following (default) location: C:\Program Files\Quest Software\NDS Migrator\Tools\mapping\linkmap.ini 24

25 Workstation Updater Reference Guide The contents are taken from the 'Volume Mappings' tab of Quest NDS Migrator: If further link paths need to be entered, add them to this file prior to running the Server Link Updater (LU.exe), OLE Link Updater action. The options of the Server Link Updater (LU.exe), OLE Link Updater are the following: Link Full Path: any local path (to the computer being updated) or a UNC path similar to '\\ServerName\ShareName' when a specific file path needs to be updated. Link Mapping File: the path to where the linkmap.ini file is currently. If this file has been changed and moved, update it here. Recursive search and update means search from the 'Link Full Path:' as a starting point and search any subfolders below it. Create a preliminary audit report: runs through the action of scanning the files, but no actual updating will be done. This is beneficial when attempting to determine how many files have OLE links. When the wizard completes, the WUPD.exe will attempt to copy the needed files and schedule a task on the remote computer (CS-MiG1-MOVEME1 for this example): 25

26 Quest NDS Migrator Where: Folder structure name is called C:\QuestSoftware\NDSMigratorWorkstationUpdaterOLE Files copied (for this action although others are copied): WUPD.EXE, LU.EXE, and Mapping\linkmap.ini' Log/HTM file(s) created: LINK_UPDATER_Date_Time_Stamp.log / LINK_UPDATER_Date_Time_Stamp.htm Scheduled Task Name: OLEUPD_COMPUTERNAME_DATETIMESTAMP The following shows a log file from the WUPD.exe on the NDS Migrator computer creating the folder structure, copying the files, and scheduling the job: 26

27 Workstation Updater Reference Guide On the remote computer (CS-MIG1-MOVEME1 for this example), when the scheduled task runs, the LU.exe is called. The linkmap.ini is cached and used for the search, find and replace action (of the LU.exe). The LU.exe parses for office documents (Word, PowerPoint and/or Excel) and opens them and looks for the link. To view the OLE link, open the office document and select Edit Links. In the Edit Links dialog box, the 'Location:' and 'Source' values are what the LU.EXE tool looks for: 27

28 Quest NDS Migrator And as seen in the 'LINK_UPDATER_Date_Time_Stamp.log' file (for this example, 'C:\Import\DaveTest= C:\Import\DaveTest1' was added to the linkmap.ini): The LU.exe can be run from the command line. To use the LU.exe at the command prompt, run the following command at the command prompt to find all the appropriate switches: LU.exe /? 28

29 Workstation Updater Reference Guide Resource Updating Monitor The Resource Updating Monitor is used to track scheduled OLE link updating (LU.exe) jobs, and the Workstation Updater Guide resource updating and workstation cleanup tasks. The Resource Updating Monitor is accessed by going to the Tools menu and selecting Resource Updating Monitor. With the Resource Updating Monitor, you can view, delete and refresh current jobs. The Resource Updating Monitor works with the 'Workstation Updater'. Once jobs are scheduled to run, they are entered into the 'Resource Updating Monitor' screen: To open the Resource Updating Monitor 1. Open NDS Migrator. 2. Select Tools Resource Updating Monitor. When jobs are scheduled to run to perform an update, the entry is added to the Resource Updating Monitor. As shown on line 17 of the sample WUPD log file below, you can see the WUPD.exe adding the job to the Resource Updating Monitor. And later on line 28, 29 you can see the Resource Updating Monitor checking the remote computers for a job status (when Refresh is selected in the GUI): The Resource Updating Monitor checks all jobs to see what the status is. This action actually pings the remote computer to see what the task "Status" is. If the computer is unavailable or cannot be contacted, the following error will be seen in the WUPD.exe log: 29

30 Quest NDS Migrator When you can contact the computer, but the job has yet to run, you will see the following error: When you can contact the computer, but the scheduled task has been deleted, you will see the following error: If this is the case, you can right-click the job in the Resource Updating Monitor and click Delete to remove it from the Resource Updating Monitor and remove errors from the subsequent logs. 30

31 About Quest Software Workstation Updater Reference Guide Now more than ever, organizations need to work smart and improve efficiency. Quest Software creates and supports smart systems management products helping our customers solve everyday IT challenges faster and easier. Visit for more information. Contacting Quest Software Mail Web site Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA USA Please refer to our Web site for regional and international office information. Contacting Quest Support Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at From SupportLink, you can do the following: Quickly find thousands of solutions (Knowledgebase articles/documents). Download patches and upgrades. Seek help from a Support engineer. Log and update your case, and check its status. View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: Support Guide.pdf. 31