Real easy question - uppercase reg entry
I hate having to ask, but.... I have a dialog that will contain a serial number for an app. The serial num needs to be in the registry in uppercase or it will not allow the app to open. The reg holds this as a string. I have a property SERIALNUM that is being correctly entered into the reg but it is not writing it in forced upper case. I am trying to use VBScript to change the value before regwrite occurs. How can I make the data ucase?
Jimm
Jimm
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
JimmPanik
15 years ago
Session.Property("SERIALNUM")=UCase(Session.Property("SERIALNUM"))
I tried that in execute deferred right before WriteRegistryValues and it did not work for some reason. Do I need the CA in a different place?
Jimm
Posted by:
JimmPanik
15 years ago
it in immediate execution
If I later make a MST that contains serial numbers for specific users, will this still operate correctly? I've problems in the past making my customizations work correctly when I install via AD GPO because the dialogs do not show.
Thanks for the help, I appreciate it.
Jimm
Posted by:
AngelD
15 years ago
If you create a transform containing the SERIALNUM property why not make sure it's in upper case?
Posted by:
JimmPanik
15 years ago
I knew you would ask.
For right now, we are deploying a repack of the app that I made. This requires minimal manual intervention in that we need to RDP to the device, start the install and enter the key #. In the future, I would like to do this based off of a GPO that is based on the user. That's where the MST would come in. I could bind a MST to a specific user and allow it to be a self install. Right now, we do not have time for this to happen.
Jimm
For right now, we are deploying a repack of the app that I made. This requires minimal manual intervention in that we need to RDP to the device, start the install and enter the key #. In the future, I would like to do this based off of a GPO that is based on the user. That's where the MST would come in. I could bind a MST to a specific user and allow it to be a self install. Right now, we do not have time for this to happen.
Jimm
Posted by:
anonymous_9363
15 years ago
ORIGINAL: JimmPanikI suspect that may have been due to having your CA in the UI sequence. Clearly, since no UI is presented in a GPO deployment, the UI sequence doesn't run therefore the CA doesn't get executed. Provided you have the CA in EI, you'll have no problem running the CA. The problem then becomes one of how you match your user against his/her serial number, given that the CA will be running in System context. In that case, you may be better of doing this via Active Setup.
I've problems in the past making my customizations work correctly when I install via AD GPO because the dialogs do not show.
Posted by:
AngelD
15 years ago
Through a vbscript custom action that would look like:
Session.Property("SERIALNUM")=UCase(Session.Property("SERIALNUM"))
Session.Property("SERIALNUM")=UCase(Session.Property("SERIALNUM"))
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.