after a lot of testing with my custom setup wich works really fine (just a lil bit modified with Orca)

I tried to distribute it with PDeploy, and thats where I start to wonder...

If i run my setup with a 'normal' Windows User pointing to the setup file, right click -> RunAs -> Domain\Admin & pwd its installed...

and finally a new Desktop Icon appear -> all looks fine and ready to deploy.

Just setup a simple Command Task locating the same setup.exe file using the same credentials for RunAs...

and how good that I had tested it once more - just rollback my VPC

PD didn't create the Desktop Icon @ my Desktop, I found it @ my root drive where it should't be, even the AppData Folder is now directly under my root drive the only correct thing are the program files nothing more.

PTClient 7.1.3 / <German>

Console 7.1.1.580 / <German>

so anyone any Idea - whats going on?

clueless cheers

Michael

• Is your custom setup a .msi file?
• What command syntax are you using to install the custom setup?
• Is the command running when the machine is logged off? That might explain why the environment variables for desktop (and similar) are not resolved properly.
• Have you tried letting it run only when a user is logged in?
• What happens if you let the command run as current user instead of as the Run As user?

Hi,

in the end it's an msi file, invoked from a setup.exe created with Microsoft Office 2003 Resource Kit / Custom Installation Wizard.

After creating this setup I modified the setup.ini Commandline CmdLine= PROGDIR=C:\lotusotes DATADIR=C:\Lotus\Notes\Data /qb /passive & changed with Orca the DesktopIcon.

After running this setup as loggedOn Windows User (with nearly no rights) by using Explorer RunAs Domain\Admin everything is correctly Installed, and I added the Command-Task \\<server>\prism$\LN-Client655-ADMIN\NETINSTALL\setup.exe

I didn' notice that it is possible to invoke a task when no user is logged one -> so I always are logged on to keep an eye on this Installation.

Setup abort and telling something about not enough rights.

cheers

Michael

k, nobody seems to got an Idea ...

meanwhile I found some other 'strange' not working cases....

I made another setup file (not the same soft as above) working great Install with msiexec uninstall with msiexec /x and all with a simple PrismDeploy cmd Task....

then i made a lil mistake .. I overwrite the existing msi package with a newer Version... after all I can't uninstalled the existing one anymore,

so I decide to install the new package ->  after the prsim install cmd task run the version remains the same, until I went to the 1st client start - > run -> msiexec /fo xxxxx.msi /q the new version appears... so far so good ;o) and now I know what kind of prism task I should run to correct my mistake... but it won't work ... prism keep telling me Warning Error 1638 (0x666) / returncode 5200 and it ain't matter if I execute a pts or cmd as local user, Domain Admin, Local Admin or System.

btw: I'm not sure but it looks like a bug, these kind of problem appears since we have had upgraded our Version from prism_suite_7.0.4.23_(de-ev-ok).exe -> prism_suite_7.1.1.580_(de-ev-ok).exe

regards

Michael

Does the command fail if you run it as the current user?  If so, have you tried creating a package of the changes that you are making with the MSI?

I'll add your scenario to the feature change item we have regarding the Run As.

ok, you got point.

I didn't expect that CU-Install will work... but it does.

Cheers,

Michael

Hi once more

It didn't work, my mistake just because I played too much and didn' t remind my custom.exe file wich start up & execute the setup as Administrator. Sorry my fault.

I had removed the my stuff from the command and just let prism deploy run the right setup.exe as current user, and it fails :-(

It looks like a little deadlock.

I don't want to use a Package just because I like to Update a specific Version, and the newer Notes Version get rid of some files, so I don't need them on my Clients HD anymore, if I would use a package I cannot ensure that these files get removed.

Any Idea how to handle this?

regards,

Michael

You could then assign the user MSI package to run as current user (and perhaps run once for each user who logs in). The machine MSI package could be assigned to run once per machine and to run as an admin-level user.

Let us know how this works for you.