I have a few *.msi installs that launch if you double click on them. However, if they're created as application objects, I get a 1603 error. Not great with *.msi installs either. Has anyone encountered this problem?
I have run into this one, all I needed to do was map a U drive for the workstation. M$ doesn't give much info from my searches on this issue, so it may be difficult to find out why you are getting it. We had to map the U drive (going to the users home directory) manauly because it was not mapping in the login script. The workstation team has the My Documents directory was redirected to the U drive.
You may need to do similar, but not exactly the same. Sounds like the system is looking for resouces, and not finding them.
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.