going to use wininstallle (free) to create MSI

[eyeball]

hi,

i just have a few questions regarding this, which i cant seem to find the answer to so here goes;

if i have 2 machines as follows:

1- fresh XP install

2- xp install

1) if i install wininstallle on machine 2 and then run it from machine 1 do i do it through UNC path or map a drive to it?

2) does the fresh install have to be 100% up to date? or can i do it using "as is"

3) does it matter if i sign the fresh XP onto a domain and then use the MSI i create on an entirely different domain?

4) also does it matter if i set a manual IP address or an address given by a dhcp server?

thank you

Edited February 14, 2006 by eyeball

[nmX.Memnoch]

1) if i install wininstallle on machine 2 and then run it from machine 1 do i do it through UNC path or map a drive to it?

UNC will probably be your best bet but I believe that WinINSTALL LE will work either way. It gives you the option to specify the UNC during install.

2) does the fresh install have to be 100% up to date? or can i do it using "as is"

"As is" should be fine.

3) does it matter if i sign the fresh XP onto a domain and then use the MSI i create on an entirely different domain?

No, this shouldn't matter.

4) also does it matter if i set a manual IP address or an address given by a dhcp server?

Again, shouldn't matter...UNC's are accessed by the machine name.

[eyeball]

excellent!

thank you very much for your reply i really appreciate it

anything i should know before i begin? or is it fairly straightforward?

[nmX.Memnoch]

It's all pretty straight forward.

[eyeball]

i have created an .MSI of realvnc however i get the whole program files directory of vnc, a reg file, a .nai file and my .msi.

if i then try to run this .msi file on any other machine it wont work unless all the files are present.

surely this isnt right?

can anyone help me please?

Edited February 15, 2006 by eyeball

[chilifrei64]

this is how winstallle works. What you need to do now is all those files should be in a network share on your server, then run the msi file from the network share.

WinstallLE was not meant to create a single-all-in-one msi file but more or less a hack to allow you to deploy software with group policies.

[nmX.Memnoch]

If I'm not mistaken the latest version of WinINSTALL LE isn't even free anymore...

[chilifrei64]

correct

[eyeball]

ok so if i put all these files in a network share and deploy via GPO it should work? il give that a try later today. thanks guys

btw i used the one from the windows server 2000 disc, i guess the newest version would be a lot better, but i dont have a budget for things like this so... lol

[chilifrei64]

I have added all sorts of applications to to be deployed via GP by using WinstallLE. I would obviously do testing on each applications. I to used the one off the windows 2000 disk, certian applications need to install they way they were intended to. The only ones I had a problem with were MSDE and Pervasive SQL client and I deployed roughly 25 other applications using this method