Common use of BAT Clause in Contracts

BAT. This file is invoked when the discovery has been specified. This is only invoked if the subnet range has been specified instead of the text file of IP addresses. It discovers the clients to see if the client is installed on the machine by checking the registry key “HKLM\SYSTEM\CurrentControlSet\Services\SmcService” if it exists on the client. This file is invoked when the discovery option has not been specified. It pings the clients and tries to copy over the files on the “c:\sylinktemp” directory on the client. It copies over the files to the client side and starts the “SylinkReplacer” service that it creates and then deletes the service once the app2.bat on the client side is invoked. The files copied over on the client are app2.bat, Sylink.Xml, esugsleep.exe, esugreg.exe and password.txt (in case a password to stop the service is specified.) This file gets invoked when the text file with IP addresses is specified. . It discovers the clients to see if the client is installed on the machine by checking the registry key “HKLM\SYSTEM\CurrentControlSet\Services\SmcService” if it exists on the client. This file gets invoked for the log gathering. It gathers the logs from the clients under %windir%\system32\ESUG. This is the file that gets executed on the client side to replace the Sylink.xml file. The helper files along with app2.bat on the client side are Sylink.Xml, esugsleep.exe, esugreg.exe and password.txt (in case a password to stop the service is specified.) This is the file that eventually replaces the original Sylink.xml This application provides a delay for processing inside the batch files. esugreg.exe This application is used to read the registry, find out the location of the SMC.exe, and the client installation location. This file contains the password in case it is needed to stop the SMCService on the client. General: -All the files in the C:\Sylinktemp on the client side are deleted along with the folder once the execution is complete and the logging is done in the directory %windor%\system32\ESUG. -On the computer where the tool is being run the c:\sylinkreplacer will not get deleted unless manually done. -If the silent run option has to be removed, the answer file located in C:\sylinkreplacer\silent by the name SylinkSilent.Settings has to be deleted manually. -It is highly recommended to run the tool with the credentials of the “Domain admin.” -This tool is designed for a domain, but can be used in a workgroup if there is a universal admin account used. -For the discovery process it is mandatory for the user executing the tool to have at least “read” permissions on the registry key “HKLM\SYSTEM\CurrentControlSet\Services\SmcService” on the client side. Question: What are the best practices for running the tool? Answer: The logged in user should be a member of the “Domain admins” group and should have at least “Read” privileges to the registry key “HKLM\SYSTEM\CurrentControlSet\Services\SmcService” on the client side in case of discovery. Question: Is it mandatory to have the c$ on the clients? Answer: Yes, It is mandatory to have the c$ on the client and c:\ on the server. Question: Why does the tool appear to run properly when executed from a windows 2000 machine but not replace the Sylink.xml on the clients? Answer: This is due to the fact that the tool uses the built in sc.exe command to create a temporary service which by default is not part of the Windows 2000(available in windows 2000 server resource kit) Question: In what environments should the discovery not be selected? Answer: It is highly recommended to run the discovery but in case there is a known problem with the registry permissions, this option can be omitted. Question: How can the 10 second wait be omitted after preparing the answer file? Answer: The best and the easiest way is to delete the sylinksilent.settings file located in c:\sylinkreplacer\silent directory. This will return the tool to it’s default “verbose” mode.

BAT. This file is invoked when the discovery has been specified. This is only invoked if the subnet range has been specified instead of the text file of IP addresses. It discovers the clients to see if the client is installed on the machine by checking the registry key “HKLM\SYSTEM\CurrentControlSet\Services\SmcService” if it exists on the client. This file is invoked when the discovery option has not been specified. It pings the clients and tries to copy over the files on the “c:\sylinktempadmin$\system32\esug\sylinktemp” directory on the client. It copies over the files to the client side and starts the “SylinkReplacer” service that it creates and then deletes the service once the app2.bat on the client side is invoked. The files copied over on the client are app2.bat, Sylink.Xml, esugsleep.exe, esugreg.exe and password.txt (in case a password to stop the service is specified.) This file gets invoked when the text file with IP addresses is specified. . It discovers the clients to see if the client is installed on the machine by checking the registry key “HKLM\SYSTEM\CurrentControlSet\Services\SmcService” if it exists on the client. This file gets invoked for the log gathering. It gathers the logs from the clients under %windir%\system32\ESUG. This is the file that gets executed on the client side to replace the Sylink.xml file. The helper files along with app2.bat on the client side are Sylink.Xml, esugsleep.exe, esugreg.exe and password.txt (in case a password to stop the service is specified.) This is the file that eventually replaces the original Sylink.xml This application provides a delay for processing inside the batch files. esugreg.exe This application is used to read the registry, find out the location of the SMC.exe, and the client installation location. This file contains the password in case it is needed to stop the SMCService on the client. General: -All the files in the C:\Sylinktemp admin$\system32\ESUG\Sylinktemp on the client side are deleted along with the folder once the execution is complete and the logging is done in the directory %windor%\system32\ESUGadmin$\system32\ESUG. -On the computer where the tool is being run the c:\sylinkreplacer will not get deleted unless manually done. -If the silent run option has to be removed, the answer file located in C:\sylinkreplacer\silent by the name SylinkSilent.Settings has to be deleted manually. -It is highly recommended to run the tool with the credentials of the “Domain admin.” -This tool is designed for a domain, but can be used in a workgroup if there is a universal admin account used. -For the discovery process it is mandatory for the user executing the tool to have at least “read” permissions on the registry key “HKLM\SYSTEM\CurrentControlSet\Services\SmcService” on the client side. Question: What are the best practices for running the tool? Answer: The logged in user should be a member of the “Domain admins” group and should have at least “Read” privileges to the registry key “HKLM\SYSTEM\CurrentControlSet\Services\SmcService” on the client side in case of discovery. Question: Is it mandatory to have the c$ admin$ on the clients? Answer: Yes, It is mandatory to have the c$ admin$ on the client and c:\ on the server. Question: Why does the tool appear to run properly when executed from a windows 2000 machine but not replace the Sylink.xml on the clients? Answer: This is due to the fact that the tool uses the built in sc.exe command to create a temporary service which by default is not part of the Windows 2000(available in windows 2000 server resource kit) Question: In what environments should the discovery not be selected? Answer: It is highly recommended to run the discovery but in case there is a known problem with the registry permissions, this option can be omitted. Question: How can the 10 second wait be omitted after preparing the answer file? Answer: The best and the easiest way is to delete the sylinksilent.settings file located in c:\sylinkreplacer\silent directory. This will return the tool to it’s default “verbose” mode.