transforms with logic
Any one have any idea on adding logic into a transform that can determine which domain the machine is on and then install a customized configuration for that domain? This customazation file is different for each domain. I want to have logic in one transform to that can can do this.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
reds4eva
16 years ago
I actually did something similar a few days ago, not domain name, but with computername. In theory it is the same-ish.
I used Wisescript to enumerate the first 3 letters from the computername and set a property, and then set a feature in the msi to use the property if it was certain letters, and another feature if it wasnt. It installed different reg settings for different computer names.
Or, the below enumerates the domain name, just give the script some parameters, someone else may elaborate.
Set objSysInfo = CreateObject("ADSystemInfo")
Wscript.Echo "Domain Name: " & objSysInfo.DomainShortName
I used Wisescript to enumerate the first 3 letters from the computername and set a property, and then set a feature in the msi to use the property if it was certain letters, and another feature if it wasnt. It installed different reg settings for different computer names.
Or, the below enumerates the domain name, just give the script some parameters, someone else may elaborate.
Set objSysInfo = CreateObject("ADSystemInfo")
Wscript.Echo "Domain Name: " & objSysInfo.DomainShortName
Posted by:
India_Repackaging
16 years ago
Hi,
I think you can add a script to determine the domain and then depending upon that you can have components installing conditionally for that particular domain.
One more thing, I dont know whether you can determine the domain without adding the script but using Windows Installer itself. I am not sure of this, but may be someone can come up with solution??[8|]
Cheers
I think you can add a script to determine the domain and then depending upon that you can have components installing conditionally for that particular domain.
One more thing, I dont know whether you can determine the domain without adding the script but using Windows Installer itself. I am not sure of this, but may be someone can come up with solution??[8|]
Cheers
Posted by:
anonymous_9363
16 years ago
ORIGINAL: India_RepackagingThere's no native way to do *the whole exercise* in WI. It has to be script of one form or another. How many domains are we talking about? It can't be many, can it? If it's manageable, you could test for the environment variable USERDOMAIN and branch accordingly. Environment variables can be used like quasi-properties - [%USERDOMAIN]. Note that in WI, unlike in DOS, only one '%' is used.
One more thing, I dont know whether you can determine the domain without adding the script but using Windows Installer itself. I am not sure of this, but may be someone can come up with solution??[8|]
Posted by:
AngelD
16 years ago
You should of course compaire the USERDOMAIN value with COMPUTERNAME as a same value would mean local logon which would not be the domain name.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
