Heterogeneous organizations looking to standardize on a single deployment tool should check out DeployStudio, a freeware monolithic imaging solution for Mac and Windows clients.
Related:Java Deployment Tool - Software Deployment Tool - Mcafee Deployment Tool - Remote Deployment Tool - Php Deployment Tool
Pages : 1 | 2 | 3>
Question & AnswerQuestion
The IBM BigFix Client Deploy Tool User Guide
Answer
NOTE: The following content applies to BigFix versions older than 9.5.5.
Starting from the 9.5.5 level, for more details about the IBM BigFix Client Deploy Tool refer to: https://www.ibm.com/support/knowledgecenter/SSQL82_9.5.0/com.ibm.bigfix.doc/Platform/Installation/c_using_the_client_deploy_tool_new.html NIX/MAC The BigFix Client Deploy tool can be used to remotely deploy clients to Windows platform machines only. If there is a need to remotely deploy the BigFix client on other platforms (i.e. Solaris, HP-UX, AIX, Red Hat Linux, Suse Linux, and Mac OS-X operating systems) use the following BigFix Agent Deployment Wizard (stand-alone) Note: This tool can also deploy Windows agents as well. WINDOWS The BigFix Client Deploy tool is included in the BigFix Installation Generator and gets installed along with the server to the BigFix EnterpriseBES InstallersBESClientDeploy directory by default. Sometimes the BES Installers directory is installed to a different directory on the server (for example: C:BESInstallers). You may need to search for this directory. The location of this folder is stored in the following registry key on the server: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeBigFixBES Installation Generator The Client Deploy Tool can be launched from the Start menu on the Windows Server Machine at Start > All Programs > IBM BigFix > IBM BigFix Client Deploy Additionally, the Client Deploy Tool can also be invoked from within the console in the Unmanaged Assets area to install a client to a specific endpoint. When you right click on an unmanaged asset in the list, you will see a menu item called 'Install IBM BigFix Client..' In version 9.0 of the console, this menu item is enabled by default. In previous versions of BigFix, if the menu item is not enabled (grayed out), you can enable it by copying the entire BESClientDeploy folder to the BigFix EnterpriseBES Console directory and restart the console (the BESClientDeploy folder will then reside at: BigFix EnterpriseBES ConsoleBESClientDeploy as well). Upon running the tool from the Start menu, you will be presented with three options to look for computers within your network for which to deploy the BigFix client to: The first and second option scan for computers within the Active Directory or within NT 4.0 domains, The third option presents with a text area to manually paste a list of known hostname, IP addresses, or an IP range; or a button to load in a file of hostnames, IP addresses, or IP ranges (one entry per line):
Note: You can also execute the CDT from the command line (see the Command Line Usage section in this article blow) while using a list file. You would do this by:
The Windows user account and password that the user enters into the Client Deploy Wizard needs to be a domain admin user with local admin rights on the endpoints for which the client will be deployed to: When it is run, the BigFix Client Deploy Tool will do the following:
The user will be presented with a list of all the computers in the network along with the status of whether the BigFix Client is installed or not; or it will report that the computer was not responding if it is offline or unreachable. The user will then be able to choose computers from the list returned and deploy the BigFix Client them using their Windows domain administrator credentials. Requirements:
If you are unable to use the BigFix Client Deployment tool for any reason, consider using a different method for BigFix Client deployment detailed in the BigFix Installation Guide.
Command Line Usage
The following are the command line parameters for the BigFix Client Deploy Tool: /useComputerNameList <computer name list file> Used to supply the path of a text file containing one NETBIOS computer name or IP address per line, which will be used for deployment, skipping over the discovery functionality of the deployment wizard. /automatic Can be used with /useComputerNameList to run without user input. Need to supply a password and possibly a username using the following flags. /password <password> /username <username> /domainNameSubstitution <old> <new> When deploying to a domain name found in active directory, this option will cause the first occurrence of the string '<old>' in the domain name to be replaced with the string '<new>' /domainNameAppend <stringToAppend> /deployRetryDelay <seconds to delay> /deployRetryCount <times to retry> A retry count of 0 will cause it to only try once. Note: The /username and /password command line options don't work in the TEM 7.2.1.357 release.
Troubleshooting Problems
Debug Logging:
To enable debug logging for the Client Deploy Tool, add the value DebugOut [REG_SZ] to the following registry key HKLMSoftwareBigFixClientDeploy. Set the value equal to a directory path and a file name (for example: C:CDTcdtdebug.log). The directory and file must exist ahead of activating the logging.
Common Errors and Problems:
The NET USE command, net use * targetcomputeradmin$ /user:domainuser password, can be used to tell you what kind of error the Client Deploy Tool is running into with the computers.
Error: System error 53 has occurred. The network path was not found. Meaning: ADMIN$ share not available. Error: System error 1219 has occurred. Multiple connections to a server or shared resource by the same user, using more than one user name, not allowed. Disconnect all previous connections to the server or shared resource and try again. Meaning: If the machine used to run the Client Deployment Tool already has a connection to remote machine ADMIN$ share, using a different credential, this error will occur. Error: System error 1311 has occurred. There are currently no logon servers available to service the logon request. Meaning: Domain server not available for authentication. Error: System error 1326 has occurred. Logon failure: unknown user name or bad password. Meaning: Incorrect admin username or password.
Error: System error 5 has occurred. Access is denied.
Meaning: Username/password correct, but account does not have permission to ADMIN$ share. Error: No network provider accepted the given network path. Meaning: The client or the server could not be resolved during the client deploy tool process. More information: The 'Access is Denied' or 'Windows Error: Logon failure: unknown user name or bad password' status indicates that the CDT is unable to connect to the computer to determine if the IEM Client is installed. In addition, It is likely that you would also be able to deploy the client through the CDT if this error is encountered. The following conditions may be causing this error message:
Increase the IRPStackSize value on the endpoint. The following Microsoft KB article gives steps on where to do this in the registry: http://support.microsoft.com/kb/106167 Retry to deploy the client after the value has been increased. If the client deploy fails with the same error message, increment the IRPStackSize value and try to deploy the client again. Checks:
Note: The destination computer in each of the ping tests should resolve to both the expected computer and the expected IP address.
Test:
Try installing the client by using the IP address. If using an IP address works, it is likely the issue is DNS related.
Microsoft Windows For MacNetwork Path Errors and Their SolutionsReason: No network provider accepted the given network path
Resolutions:
Internal Use Only
04/03/2017 - I added at the beginning of the Answer section a note.
Related URL
[{'Product':{'code':'SSBQVS','label':'IBM BigFix family'},'Business Unit':{'code':'BU008','label':'Security'},'Component':'Client','Platform':[{'code':'PF025','label':'Platform Independent'}],'Version':'Version Independent','Edition':'}]
Product Alias/Synonym
IBM BigFix;IBM Endpoint Manager;Tivoli Endpoint Manager
Windows Mac OsDocument InformationComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |