I have been having problems making packages with WinInstall LE. We use a roaming .MAN profile for all users does this cause a problem when a piece of software if it wants to make profile changes?
If you have the most recent version of WinInstall LE (v2003), you can remove or add the .MAN file from the profile so that the package does not care about them.
Although WinInstall sounds easy, I rarely hit a package that does not need a little work afterwards for it to install properly.
"In space, nobody can hear you click..."
Yeh thanks i have got Wininstall 2003 now it is better that 2000 but still a few probs.
If you don't mind answering a couple of questions.
Some packages tell me to run validation when i add them to a GP how do i do this?
Some software already comes with an msi but after i distribute it i have to put in the Key, is there a way to add the key to the ready made package without having to repackage the whole app?
Running validation... I think that only means that you need to add the MSI package to the GPO from the computer that has WinInstall on it. I've seen this problem after I slipstreamed Office 2000 to SP3. I could not seem to add the package from my station and there was a KB saying that it had to be added from the RIS computer itself. It worked. I hope that's your issue.
For the serial numbers, check in the W2K forum. heh I answered you there...
"In space, nobody can hear you click..."
What sort of software are you trying to repackage and install with Wininstall ?
It sounds to me like you need to create either an administrative installation or a MST-file for the serial.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.