By default, Express Software Manager identifies computers by comparing three variables: the name of the machine, the address of the network card (NIC), and the serial number of the hard drives. If two or more of these identifying variables match information in the existing Applib.mch file, the data gathered will be stored in a corresponding .INV file.
Gensmsid.exe creates a file called Sms.ini (if it does not already exist) in the root of the PC's first hard drive and inserts a unique 19-character ID number into the Sms.ini. You can then change the Machine re-identification method to SMS ID and Express can then use these ID numbers to uniquely identify ghosted machines. Because this guarantees that each machine in the library has a unique identifier, the use of the SMS ID prevents machines from overwriting each otherÂ’s data even if they have the same hard drive serial number and machine name.
Note: If SMS 1.2 has already been deployed in your environment, the Gensmsid utility detects the existing Sms.ini and will NOT overwrite it. (The -o switch can be used to overwrite an existing Sms.ini file.) If you attempt to deploy SMS 2.0 after the Gensmsid utility has been run, there should not be any conflict because SMS 2.0 does not utilize to the Sms.ini file.
By default, Express Software Manager identifies computers by comparing three variables: the name of the machine, the address of the network card (NIC), and the serial number of the hard drives. If two or more of these identifying variables match information in the existing Applib.mch file, the data gathered will be stored in a corresponding .INV file.
Gensmsid.exe creates a file called Sms.ini (if it does not already exist) in the root of the PC's first hard drive and inserts a unique 19-character ID number into the Sms.ini. You can then change the Machine re-identification method to SMS ID and Express can then use these ID numbers to uniquely identify ghosted machines. Because this guarantees that each machine in the library has a unique identifier, the use of the SMS ID prevents machines from overwriting each others data even if they have the same hard drive serial number and machine name.
Note: If SMS 1.2 has already been deployed in your environment, the Gensmsid utility detects the existing Sms.ini and will NOT overwrite it. (The -o switch can be used to overwrite an existing Sms.ini file.) If you attempt to deploy SMS 2.0 after the Gensmsid utility has been run, there should not be any conflict because SMS 2.0 does not utilize to the Sms.ini file.
Reviews related to Express Metrix, LLC Express Software Manager
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
