Windows Agent Deployment

Transcription

LabTech
WINDOWS AGENT DEPLOYMENT ................................................................................................................................................................................................................................................................................................................................................. 1
Overview ................................................................................................................................... 1
What Method Should I Use to Deploy Agents? .................................................................... 1
What is Required Before I Deploy? ....................................................................................... 2
Client Administrative Settings ............................................................................................... 2
Agent Deployment Settings.................................................................................................... 4
Downloading the Agent Installation File ............................................................................... 6
Agents Deployed via Login Script ......................................................................................... 8
Agents Deployed Manually ..................................................................................................... 9
Agents Deployed via GPO ...................................................................................................... 9
Agents Deployed via Probe Push ........................................................................................ 10
Agents Deployed by LabTech Deployment Script ............................................................. 25
Using the Deployment Script to Deploy to a Specific IP ................................................... 27
Agent Installation via Network Devices .............................................................................. 28
Agent Installation on Server Core 2008 .............................................................................. 30
Agent_Install.exe Command Line Parameters ................................................................... 30
Troubleshooting .................................................................................................................... 30
Network Probe Scan Not Successful ................................................................................ 30
Partial LabTech Reinstall Fix ............................................................................................ 31
.NET Cleanup .................................................................................................................... 32
LTAgent not checking in/offline ......................................................................................... 32
Agent Duplicating in Control Center.................................................................................. 32
Document Revision History.................................................................................................. 32
Overview
LabTech agents are client applications that run as a service on a computer, and
enable it to report into your LabTech server for reporting, monitoring, script execution,
etc. Computers running the LabTech agent are sometimes referred to as agent
computers, remote computers or just remotes. Before you deploy agents, the client
and location must be configured in LabTech.
The LabTech agent can be deployed through several methods. The agent may be
installed on the workstation or server manually, through a login script, by group policy
(GPO) or pushed by the network probe.
What Method Should I Use to Deploy Agents?
The environment to which you are deploying to should determine the best distribution
to use. Here are some guidelines to consider when choosing which method to use:
1A.51.155.WindowsAgentDeployment.docx
1
Figure 1: Deployment Suggestions
What is Required Before I Deploy?



Clients and Locations must be set up and configured, including the
Passwords and Deployment & Defaults tab. Default template needs to be
configured. If using custom templates, at least one needs to be configured
for deployment.
.NET Framework 2.0 (minimum) is required for the installer to run; if you are
not using the probe (the probe will automatically install .NET). LabTech
recommends using version 3.5, SP1.
Verify AV Exclusions:
o For folders:
 Add %windir%\ltsvc | %windir%\temp\ltcache |
%windir%\temp\_ltupdate
o For file exclusions:
 Add %windir%\ltsvc\lltray.exe | %windir%\ltsvc\ltsvc.exe |
%windir%\ltsvc\ltsvcmon.exe
Client Administrative Settings
Clients must be configured prior to deploying any agents. If you have not already
added your clients to LabTech, do so now before continuing. Once your clients have
been added, you are ready to continue.
NOTE: If you want more detailed information on setting up clients, please refer to the
Client Management documentation.
2
LabTech
1. In the Control Center, on the navigation tree, right-click on a client. Select
Modify Client from the menu that displays or simply double-click on the client.
Figure 2: Client Screen—General Information
2. Complete any remaining fields on the General screen.
3. Click on the Passwords tab.
4. You must add at least one administrative account. Right-click in the white area
of the screen. From the menu that displays, select Add Entry.
3
Figure 3: Passwords—Add Administrative Account
5. Enter the type of password in the Title field.
6. Enter your domain\user name in the User Name field (e.g.,
simpledomainname\administrator. The domain must not not exceed 15
characters – use the name assigned by Windows.
7. Skip the URL field. This is for non-administrative passwords.
8. Enter the administrator password in the Password field and Repeat in the next.
9. Complete the Notes, Location and Expires field, if desired and click OK.
10. Click Save to save your changes.
Agent Deployment Settings
The agent deployment settings are set in Deployment & Defaults tab of the location.
These must be configured prior to deploying any agents. This screen allows you to
configure the default group for agents, administrative access, templates and alerting
defaults by location.
The following steps assume that you have already created the target client and
location to which you are deploying. If you have not done so, please set this up
before continuing. If you configured the Deployment & Defaults when you added
4
LabTech
your locations, you may want to go back and verify your settings before proceeding
with your deployment.
The location’s custom agent installer is created using the values entered in the
Deployment & Defaults screen.
1. In the Control Center, double-click the client’s location that you want to
configure the deployment and default options for, or right-click and select
Locations > Modify Location.
2. Click on the Deployment & Defaults tab. This screen covers multiple areas.
The only section related to deployments is the Agent Deployment Settings
section.
Figure 4: Location—Deployment & Defaults tab
3. Select ‘Not Selected’ in the Default Group for New Agents field. Auto-join
scripts handle this functionality.
4. Select the Login to use for Administrative Access from the drop-down list.
This login is used to install the agent (when using the agent installer executable)
and perform other administrative functions after the agent is installed. This
password will be the default password used when performing the following:

When commands are issued that require administrative credentials, this is
the default used.

Commands including pushing LabTech and running other administrative
commands from the command prompt with the #prefix, this password will be
used.

Using some script functions (e.g., Shell as Admin and Execute as Admin).
5
NOTE: This list is populated from the Passwords tab. If you see ‘No Passwords for
Location’, you will need to set these up before continuing.
5. Select the Template to include in deployment package from the drop-down
list. The template selected will be the template that is used to build the
deployment package. It will not be applied to existing agents, only agents that
are installed using the custom agent installer. The benefits of configuring
templates (modifications such as branding) are immediately realized after
installing the agent. Best practice is to use the ‘Default’ template and create
additional custom templates for out of the norm scenarios.
6. Click on Save if you made any changes and close this window when finished.
7. Repeat the above steps for any other clients you need to deploy to, if necessary.
Downloading the Agent Installation File
LabTech provides a default and custom agent installer that will allow you to install
LabTech agents from any location. To retrieve the build file that will install the agent,
follow these steps:
NOTE: The default agent installer uses the information from the Deployments &
Defaults tab of the New Computers location to create the installer. If the New
Computers location is modified, the default agent settings will be changed and all
subsequent agent installations will use the new default settings. Before downloading
the agent installer, be sure that your clients and locations are configured.
1. Navigate to your LabTech server’s Web Control Center. This can be accessed
by entering your LabTech servers FQDN: http://your.labtechserver.fqdn (use
https://when applicable).
NOTE: The default agent installation package is built partially from the URL that is
typed into the browser to reach the LabTech webpage. Therefore, if you type
‘localhost’ on the server to download the default agent installation package, it will not
be a publicly working installation package. You should always use the FQDN (with
https:// when applicable) for the proper deployment package.
6
LabTech
NOTE: If you are having issues accessing the Web Control Center, be sure you
have Allow Web Access selected in the the User’s Permissions tab and ‘All
Clients’ (if you want the user to have access to all clients) appears in the Group
Membership section of the Groups and Clients tab. It is recommended that you do
not give web access to a ‘super admin’ because SQL injection tests are bypassed.
For step-by- step instructions for adding users, please refer to the User Access
documentation.
Figure 5: Web Control Center—Log in Page
2. The default agent installer can be installed from the main page. The default
installer will not contain any location specific configuration so any agent installed
as such will appear in the ‘New Computers’ location and will need to be moved to
the appropriate location. Log in with the credentials used to log in to the Control
Center to download any custom agent installers.
7
Figure 6: Web Control Center—Deployment List
3. Customized agent installers ready for download will be listed under the
Deployment List section. Click on the desired agent installer to download.
When prompted to run or save, click Save. Please note that the installers are
named identically, so you may want to create a library to track agent installations
or rename the executable. The .exe version would be used for login scripts and
the .msi is for GPO (there is no longer a need for .mst files).
TIP: If a template and administrative password have not been assigned to the
location in the Deployment & Defaults tab, you will not see a custom installer for this
location.
Agents Deployed via Login Script
Agent installation via the login script is the recommended method of deploying
agents in environments that have more than 25 agents or do not have a domain
controller.
1. Verify that the .NET v2.0 or better is installed. LabTech recommends using .NET
v3.5, SP1.
2. Download the client’s custom agent installer from the Web Control Center to the
domain controller’s netlogon folder. The netlogon’s real location is
%windir%sysvol\sysvol\domain.com\scripts. For additional information on the
Netlogon directory, please refer to the Microsoft site.
NOTE: If you need step-by-step instructions on how to access/download from the
Web Control Center, please refer to the Downloading the Agent Installation File
section earlier in this document.
3. Edit the login batch file used for the client by adding the custom agent installer
(agent_install.exe) to the end of the file.
copy\\[servername]]\netlogon\agent_install.exe%windir%\temp
call %windir%\temp\agent_install.exe /s
8
LabTech
NOTE: By using the /s, it will be installed silently and you will not be notified if the
agent was already installed. For other command line parameters, refer to the
Agent_Install.exe Command Line Parameters section.
Agents Deployed Manually
Manually installing the LabTech agent is the least desirable option, in most cases
because of the amount of time it takes if you have numerous computers to install it
on. It is recommended to use if you have less than 10 clients. If you are having
issues with any of the other methods, you should try installing manually.
To manually install the agent, you may do any of the following:


Log in to the computer and use the default agent installer. The default agent
installer can be downloaded from the main page of the Web Control Center.
Log in to the computer and use the custom agent installer. The custom
agent installer can be downloaded from the Web Control Center, after
logging in.
NOTE: If for some reason you are unable to access your client’s computers remotely
via RDP (remote desktop protocol) or the client wants to install the agent themselves,
you can give them temporary access to the Web Control Center by adding them as
a user with limited access.
Agents Deployed via GPO
Agent installation by GPO is the recommended and most reliable method of
deploying agents in environments that have more than 25 agents. If you choose to
use the group policy method for deployment, it is important to note that your clients
must have the correct .NET framework installed (regardless of which method you
choose to deploy agents). If it is not installed, the agent will not install properly. You
can put it into the same group policy as the LabTech agent installer. Refer to this
Microsoft KB article, .NET framework in a group policy object in Active Directory
for additional information.
NOTE: Refer to the MS KB article on, How to Use Group Policy to remotely
install software in Windows Server 2003 and in Windows Server 2008 if you
need information on how to create a group policy.
The following instructions will walk you through downloading the LabTech Agent .msi
file. If you need assistance with group policy, please refer to the links given above.
1. Open a browser window and navigate to your LabTech server. This will take you
to the home page of the Web Control Center.
2. Enter your LabTech Username and Password. Click Login. You must be set
up as a user in LabTech and have Allow Web Access permissions to access.
9
Figure 7: Web Control Center
3. Select the appropriate MSI package for the desired location from the drop-down
and click on Generate MSI Package.
4. You will be prompted to save the file. Click Save.
5. Navigate to the location you want to save it to and click Save. Please note that if
you are creating multiple MSI packages, they are all named Agent_Install. It is
recommended that you rename Agent_Install.msi to Client-Location.msi.
NOTE: An .mst file is no longer necessary.
Agents Deployed via Probe Push
A network probe is a service running on a designated computer per location that will
scan the network for other devices without the LabTech agent installed on them. The
probe will scan the network when the service is started, then once a day (default
setting).
IMPORTANT: The probe push will fail if the following conditions are met: Antivirus
software is set to block VBScripts, antivirus software is set to block PSEXEC.exe. or
the Windows Firewall is enabled or any additional 3rd party firewall is enabled.
Enabling the Network Probe also enables:



SNMP Trapping
TFTP Server
Syslog Event Trapping
Agent installation by network probe is one of the recommended methods of deploying
agents in environments that have more than 25 agents.
In order to set up a probe, there must be an agent already installed in the location.
The agent you use for the probe should be a computer that is constantly online and
infrequently used. You do not need to install the .NET framework, it will automatically
install with the probe.
10
LabTech
Please note that if you change any information for a client (e.g., location) or the push
is not working, it is best to refresh the installer.
1. To refresh the installer, right-click on the probe-enabled computer on the
navigation tree.
2. Select Commands > Probe > Refresh Push Installer (LTSilent).
NOTE: If the router between the probe machine and the targeted network devices
caches ARPs, the probe will be able to recognize the devices but will not be able to
obtain their MAC addresses, unless the devices are SNMP-enabled. If they are
SNMP-enabled, LabTech can query them for the MAC address and they will be
added to the system. In addition, any IP addresses that the probe finds in the scan
range that it cannot identify will not be discarded; these devices will show up in
Unknown Devices under the Network node of the navigation tree.
To configure the probe, follow the steps listed below:
1. Double-click on the client or location on the navigation tree and click on the
Passwords tab.
Figure 8: Double-click on Location
11
Figure 9: Client Location—Passwords tab
2. If the administrative account that you want to use for the probe does not exist,
right-click anywhere in this window and from the menu that displays, select Add
Entry.
12
LabTech
Figure 10: Edit Entry
3. Add the desired administrator account.
a) Enter the Title (e.g., Administrator).
b) Enter the User Name in domain\username (e.g.,
yourcorporatedomain\admin) format. The domain must not not exceed 15
characters – use the name assigned by Windows.
c) If you enter the URL to the website that is associated with this location, you
can open the website from within LabTech. If desired, enter the URL to the
website that the password is associated with. You can use replacements for
the password and username to auto replace in the URL (e.g.,
http://www.mywebsite.com/?user=%user%&password=%password%). In
addition, you can use %title%, %notes% and %router% to use the current
external IP address of the location. Once added, you can right-click on the
URL and select Open URL from the main Passwords tab to open the
website from within LabTech.
d) Enter the Password. Click on the Ellipsis button to display the password.
Please note that special characters in the Password field do not work with
the probe push.
e) Enter the password again in the Repeat field.
13
f)
Enter any notes.
g) Leave the Expires field unchecked.
h) Click OK.
4. Click on the Deployments & Defaults tab. This screen covers multiple areas.
The only section related to deployments is the Agent Deployment Settings
section.
Figure 11: Deployment & Defaults tab
5. Leave the Default Group for New Agents ‘Not Selected’.
6. Select the Login to use for Administrator Access from the drop-down list.
7. Select the Template to include in the deployment package from the dropdown list.
8. Click Save and close this window.
9. Double-click on the template (the one you included in the deployment package)
from the navigation tree. On the Agent Settings tab, select the Turn on Agent
Debug Logging checkbox to enable debugging.
14
LabTech
Figure 12: Template Configuration—Agent Settings: Debugging Enabled
10. Double-click on the computer on the navigation tree that you want to be used as
the probe.
Figure 13: Computer—Welcome screen
11. Select Network Probe. You will be prompted to confirm the enabling of the
network probe on this computer.
15
Figure 14: Enable Network Probe
NOTE: If the probe is already enabled on another computer, you will be prompted to
move the probe to this computer. Click Yes if you want to move the probe or No to
cancel.
12. Click Yes to continue. This will start the Probe Express Setup Wizard.
Figure 15: Probe Express Setup Wizard
13. Click Next.
16
LabTech
Figure 16: Deployment Settings
Any passwords that are currently set up for this client will display here. Passwords
are typically set up by Location in the Passwords tab.
14. The probe requires the use of an administrative account for agent deployment. If
necessary, add an administrative user to the list by right-clicking on the list and
selecting Add Entry from the menu. User names must include your domain or ‘.\’
for local accounts (e.g., abccomputers\AAndrews or .\AAndrews).
NOTE: Please note that the user you add in the list will not automatically populate
the Passwords tab in the Location. If you want it on the Passwords tab, you will
have to update it manually with the entry you just added.
15. Select the administrative login you want to use from the Login to use for
Administrative Access drop-down. This field is required. Using the example
above, you would have ‘Admin’ and ‘System Engineer’ as options to choose
from.
16. Select the template you want to use for your agent deployment from the
Template to include in deployment package drop-down. This field is required.
17. Click Next to continue.
17
Figure 17: Detection Settings
18
LabTech
NOTE: Community strings are used in the communication process between the
probe and SNMP enabled network devices. Depending on the manufacturer, a
default value for the community string is often public. Almost all network devices
support SNMP V1/V2c, both of which require a community string as a pass-phrase.
Most manufacturers configure devices with a read-only community string of ‘public’.
In order for the probe to communicate the string must match the device’s internally
configured community string.
18. The Community Strings field is automatically populated with public, private and
admin and should cover the majority, if not all of your SNMP devices. Add any
additional strings, if necessary separated by commas.
TIP: It is recommended that you have no more than 4-5 different strings as each
string represents an additional test the probe must perform. Strings should be
ordered in preferred search order, with the most often used strings first.
19. In addition to finding devices through a simple ping, the probe attempts to find
network devices by opening commonly used ports. The Scanning Ports field
defaults to port 80 (web), 21 (FTP) and 23 (Telnet). These will be the most likely
ports that you will want to scan. Enter any additional ports you want scanned,
separated by commas. Please note that each additional port you add does add
processing costs so only add ports that are necessary to scan.
20. The Scan Frequency defaults to once a day. This is how often the probe will
scan the network for new devices. Select the desired frequency from the dropdown. Times range from five minutes up to one day. Keep in mind that scanning
can be intensive on networks of more than a few devices; therefore it is
recommended that you do not set the frequency for less than an hour.
21. Select the Collection Network Device Data for this Location to start collecting
data on every device at this location. This allows you to select which locations
you want to collect data for. Please note that this will increase your bandwidth
usage and disk usage on the LabTech server.
22. Click Next.
19
Figure 18: Probe Setup Complete
23. Click Finish to complete the initial setup. When an agent becomes a probe, it
downloads all of the necessary tools it requires, including .net installers. This
process may take several minutes. When it is complete, you will see the
Network Probe flag selected and the Network Probe tab display on the
Computer screen as shown below.
Figure 19: Network Probe Tab
24. Click on the Network Probe tab. The basic settings have already been
completed by using the wizard.
20
LabTech
Figure 20: Network Probe—General Settings
25. The Passwords to Attempt field will already be populated with the values you
entered during the wizard. If you want to add additional passwords to use for the
probe, select the administrator account(s) you want to use from the drop-down
list and click Add. The selected administrator account(s) should now display in
the Passwords to Attempt field. These are the passwords the probe will use to
attempt the LabTech agent install. It will try the top one first and then work its
way down the list if the previous one did not work, until there are no further
passwords to try. Use the Down and Up buttons to move passwords up or down
in the list.
NOTE: The Passwords drop-down list is populated from the passwords set in the
Passwords tab of the Client and Location screen. The Add button will add the
password to the Passwords to Attempt field. The Delete button will remove the
password.
26. Select the Enable Automatic Network Installation checkbox to signal the probe
to install LabTech on all Windows machines the next time the computer is fully
scanned, which could be up to a week (depends on what your scan frequency is
set at) for detected computers.
27. Enter any additional information pertaining to the probe in the Comments and
Info field. For example, if you have a printer being disposed of in the next month
you can indicate in the notes that you do not want to include a specific IP
address in the scan range.
28. The Search Me field is currently not in use.
29. If you are recording serial numbers, you can enter the Serial Number. However,
this field is not required and is not used in any reporting.
30. Select the alert template to use for when a SNMP trap is received or a Syslog
event occurs. For instructions on how to create a new alert template or for
additional information on the alert templates, please refer to the Alert Templates
documentation.
21
Figure 21: Network Probe Configuration—Scan Settings
31. The Frequency field is automatically populated based on the information you
entered during the Probe Wizard. The frequency dictates how often the probe
will scan the network for new devices. If you want to make changes, just select
the new frequency from the drop-down.
32. The Scanning Ports field is also automatically populated based on the
information you entered during the Probe Wizard. Enter any additional ports you
want scanned, separated by commas. Please note that each additional port you
add does add processing costs so only add ports that are necessary to scan.
33. The Ping Timeout defaults to 50 milliseconds. For heavy traffic networks, you
may want to adjust this time to approximately 75 because it will take longer for
the ping results to return.
34. The Port Scan Timeout also defaults to 50 milliseconds. After the ping, the
probe will attempt to scan the ports that appear in the Scanning Ports field and
will time out after the specified time period.
35. The network probe scans based on the IP and count. Specify the Subnets that
you want the probe to start scanning. Enter the Subnet (e.g., 192.168.1.1, must
not end in 0) and 253 in the Count field and click Add IP. Count is equal to the
number of additional hosts you want to scan for, typically this will be set to 253
(because you do not want to count 0 and 255). In the example below, the probe
will start scanning at 192.168.1.1 and will continue scanning the network range
until it reaches 192.168.1.254.
Figure 22: Network Probe Configuration—TFTP Settings
36. The TFTP Settings will allow you to enter the allowed IP addresses. Enter a
comma separated list of IP addresses that you want to allow to connect to the
TFTP server (probe computer). Leave blank for all connections.
37. The Listening Port is the port it will listen on. The default TFTP port is 69. Set
to ‘0’ to disable TFTP.
38. Select the Allow Upload checkbox to allow files to be uploaded to the probe
machine. Uploads are disabled by default.
22
LabTech
Figure 23: Network Probe Configuration—Syslog Settings
The Syslog Settings will allow you to limit received syslog events from specific IP
addresses. Any syslog messages from a valid IP address are stored to a text file on
the probe computer and then periodically transmitted to the LabTech server. Syslog
messages are transmitted in batches of 300 at a time. Any additional messages are
not transmitted. So if you are performing any monitoring on received events at the
server, make sure the amount of syslog messages sent to the probe is limited as
much as possible. For selective monitoring, it is recommended to use the syslog
filters (see syslog documentation).
39. Enter a comma separated list of IP addresses that you want to receive syslog
events in the IP Filter field; otherwise if left blank, syslog events will be created
for all events.
40. The Trap Port is the port it will listen on. The default syslog port is port 514. Set
to ‘0’ to disable syslog for this probe.
Figure 24: Network Probe Configuration—SNMP Settings
41. The Community Strings field in the SNMP Settings section determines what
community strings to try when scanning devices via SNMP. This field is
automatically populated based on information you entered during the Probe
Wizard. Enter any additional community strings separated by commas. Strings
will be tried in the order they appear in the list so it is recommended to use the
most common first.
IMPORTANT: Please note that the probe will try all strings on all found IP
addresses, so each string will increase the total time of a network scan dramatically.
42. The Trap Port is the port it will listen on. The default SNMP port is port 162. Set
to ‘0’ to disable SNMP trap listening.
43. The SNMP Timeout field will default to 15 seconds. If you plan on doing a large
portion of SNMP walks on a heavy traffic network, you may want to change the
value to 45 to allow enough time for a SNMP response from the device.
Figure 25: Network Probe Configuration—SNMP V3 Settings
23
44. For each probe, the system allows for the setting of one universal SNMP V3
access combination that can be tried on all found devices. SNMP V3 is only
attempted if the Username field is not empty. Enter the Username to use SNMP
V3; otherwise skip steps 45-48 to bypass.
NOTE: The recommended practice is to not use the SNMP v3 settings. Devices in
v3 may send alarms when an incorrect password is used and the probe could cause
those alarms to fire generating false alarms. The only time you should use this is if
all your v3 devices use the same password.
45. Enter the authentication phrase for the devices that are configured for
authentication in the Auth Password field. This value needs to match all SNMP
v3 enabled devices.
46. Select ‘MD5 (Message Digest 5)’ or ‘SHA (Secure Hash Algorithm)’ from the
authentication Method drop-down. This value needs to match the device.
47. Enter the encryption phrase for the devices that are configured for encryption in
the Enc Password field. This value needs to match the device.
48. Select the encryption Method from the drop-down. The available choices are:
DES, AES, and 3DES. This value needs to match the device.
NOTE: Select the Reveal Passwords checkbox to show the passwords. Select
again (no checkmark) to hide the passwords.
49. Click the Save button to save your settings. By clicking Save, a command will
automatically be sent to rescan the network.
NOTE: At any time, you can click Rescan Network and Reinventory Devices to
scan the network and reinventory network devices.
50. Confirm the network probe is scanning the network. Click on the Probe
Commands tab. You should see a message similar to “Command Issued” in the
Output column.
Figure 26: Probe Commands tab
51. Basic setup is complete and for the majority of Partners, no additional
configuration is necessary. The probe will use its library of known devices for
discovery. However, advanced configuration using detection and collection
templates will allow you to classify the devices that the probe finds and allow you
to define the information that should be collected from these devices. It is highly
recommended that you review all of the Probe documentation to determine if the
advanced configuration will benefit you and your business.
24
LabTech
TIP: For more information on how the probe is progressing, double-click on the
probe-enabled computer from the Control Center’s navigation tree. Select the Tools,
Tasks & Groups tab. When a scan is completed, it will show ‘Done’ in the Probe
Scan Position.
Agents Deployed by LabTech Deployment Script
The LabTech Deployment script must be run from a probe computer. The probe
should be a domain controller and the domain password must be set for the probe’s
locations.
The deployment script will update the LTSilent.exe on the probe before it runs. This
will ensure that the script is updated with any new settings or passwords from the
location. It script will also get a new VBScript every time its run to ensure it has any
new changes.
This script will email a report to the contact associated to the computer that the probe
is enabled or you can create a property named DomainPushEmailOverride in
Dashboard > Config > Configurations > Properties to override the default contact.
NOTE: If an email is not being received, look at the script log on the computer as it
will be logged here. Also, make sure to check the failed emails (Dashboard >
Management > Failed Emails.
A couple of things to keep in mind:


This script does not require you to setup any settings on the Probe tab. You
only need to enable the probe and set an administrator password in the
location’s Deployment tab.
REMEMBER to wait however long it’s going to take the probe computer to
download 50mb from Microsoft. It has to get the framework files before you
run the deployment script.
To use the LabTech deployment script with a probe enabled computer, follow the
steps listed below:
1. From the Control Center, right-click on the group where the probe enabled
computer resides. From the menu that displays, select Scripts > System
Commands > Deployment > Push LabTech to Domain.
NOTE: The Push LabTech to Domain option is also available to schedule on a
client, location or the probe computer.
25
Figure 27: Push LabTech to Domain—Schedule Script
2. Select the appropriate settings and click Create.
3. Double-click on the group in the navigation tree and select the Scripts tab to
display the script schedule.
26
LabTech
Figure 28: Script Status—Queued
NOTE: You can modify the script schedule from this screen. After changes are
made, click Save. The changes will take effect immediately.
Using the Deployment Script to Deploy to a Specific IP
To use the LabTech deployment script to deploy an agent to a specific IP address,
follow the steps listed below:
1. From the Control Center, right-click on the network probe machine. From the
menu that displays, select Commands > Probe > Push LabTech to PC.
27
Figure 29: Enter Hostname or IP Address
2. Enter the Hostname or IP address of the computer you want to push the
LabTech Agent to and click OK.
3. LabTech will immediately issue the command. You can check the status of the
command by double-clicking on the probe-enabled computer, and then select
Network Probe > Probe Commands.
Figure 30: Probe Command Status
Agent Installation via Network Devices
This method is used if you want to pick and choose which workstations and servers
you want to push to after the network probe has detected all of the devices on the
network.
1. From the Control Center, expand Clients > Client > Location to get to the
desired location of where the network probe is located.
2. Expand Network.
28
LabTech
Figure 31: Network Node
All detected network devices will display.
3. Double-click on the desired computer.
Figure 32: Network Device Properties
4. Click Install. This will send a command to the network probe to install the agent
with the configuration that has been specified for this location.
29
Agent Installation on Server Core 2008
1. Edit the machine.config file located in the
%windir%\microsoft.net\framework64\v2.0.50727\config folder.
Where: locate the final closing </configuration> tag, and append the following:
<system.net> <defaultProxy> <proxy usesystemdefault="false"
bypassonlocal="true" /> </defaultProxy> </system.net>
2. Start the LabTech service by running SC START LTService.
Agent_Install.exe Command Line Parameters
Table 1: Command Line Parameters
Parameter
Description
/h
Options.Help
/s
Options.Silent (turns off the pop-up message and instead displays
console message)
/q
Options.Quiet (turns off the pop-up message and console message)
Need to use /s when you use /q, but /s can be used by itself.
/u
Options.ServiceAsUser
address=
Options.Address
pass=
Options.ServerPass
location=
Options.LocationID
user_name=
Options.LogonUsername
password=
Options.LogonPassword
proxy=
Options.ProxyServer
proxyuser=
Options.ProxyUsername
proxypass=
Options.ProxyPassword
Troubleshooting
Network Probe Scan Not Successful
Issues can sometimes be caused by ARP caching problems for one of the hardware
devices on the network. If this can be turned off and then have the network probe rescan, this will often will correct the issue.
1. If the initial scan is not successful, send the following command to the network
probe from the CMD prompt: netsh interface ip delete arpcache.
2. Re-scan the network.
3. From the Control Center, expand the Location, then the Network to see if any
new devices are listed.
4. Double-click on one of the devices.
30
LabTech
Figure 33: Network Device—Install
5. Click Install to try to install the agent.
6. If agent does not install successfully and check-in, troubleshoot the agent:
a) Check AV exceptions
b) Verify .NET is installed and enabled
c) Look for partial installs shown by existence of registry keys, etc.
7. If the probe computer will not enable at all, use the agent uninstaller, then
reinstall with the default agent install and not a customized deployment package
and try to enable again. If the location will not allow it, create a new location and
move the network probe agent to it.
Partial LabTech Reinstall Fix
In the event that LabTech only partially installed, follow the steps listed below:
1. Stop the LabTech Agent Service (if you have it).
2. Kill the LabTech Agent processes from the Task Manager.
3. Navigate to HKLM\Software\LabTech and delete the key ‘labtech’ from the
remote computer.
4. Delete the folder LTSVC from system drive\windows.
5. Reboot the computer.
31
6. Re-run the agent installer to install the LabTech agent.
.NET Cleanup
Problems can occur with the .NET install preventing the agent installation. There is
an automated cleanup tool that will remove selected versions of the .NET framework
from a computer. This tool should be used as a last resort where install, uninstall or
repair did not succeed. It is not intended as a substitute for the standard uninstall
procedure. This cleanup tool will also delete shared files and registry keys used by
other versions of the .NET framework. If you run the cleanup tool, you will need to
perform a repair or reinstall for all other versions of the .NET framework that are on
the computer or they will not work correctly afterwards. For a complete user’s guide
on the cleanup tool, refer to this web article.
Download .NET Framework Cleanup Tool
LTAgent not checking in/offline
1. Check agent system to see if LT processes are running.
2. Check AV for exceptions for all possible scan types.
3. Can the agent system reach the FQDN in browser (IIS problem or site blocked)?
4. Try uninstall, remove reg keys and LT folder, and reinstall agent, if isolated
incident.
5. Windows\LTSvc\LTErrors.txt log, Registry values in
HKLM\software\labtech\service (is there an “ID”, “password”, “serveraddress”
and “server password” key?) and HKLM\software\labtech\service\settings, LTSvc
and LTSvcMon both running? What accounts are they running under?
Agent Duplicating in Control Center
1. Delete all instances of agent system that duplicates.
2. Get registry info from labtech\service and labtech\service\settings keys. Get
LTErorrs.txt. Check event logs (could be a .net issue).
3. Uninstall agent, remove registry keys, and reinstall the default agent installer.
Document Revision History
Date
Notes
03/22/2011
Updated for 2011 release
05/10/2011
Changed AV File/Folder Exclusions
10/17/2011
Added agent install via network devices option and updated
icons.
10/19/2011
Fixed menu option for deployment script and added additional
information about the default deployment package.
01/13/2013
Added command line parameters
02/18/2013
Added additional information about adding administrator
accounts – domain must not exceed 15 characters. If it
exceeds 15 characters use the name assigned by Windows.
32

Windows Agent Deployment

Transcription

Similar documents

Bovine • Equine • Ovine • Caprine • Porcine - vaucluse

Preoperative Measurements and Intraocular Lens

Video Borescope RIGEL UF 4.0mm Brochure

Probe Year in Review

CRYOGEN-FREE Models

moJel121 ".2)rill .JJole "* (}eiger Counter

Saf-T-Log ® Thermomètre enregistreur HACCP

Technical data sheet Electro ejaculator

BORESCOPES - More than meets the eye - Part 2

LabTech Software Vendor Partner Solutions for IT

Ficha Técnica Analizador de Química Clínica BS-400

LabTech 2011.2 Upgrade