Error 1603 SMS 2003 SDEployment
Hi,
I am new to SMS 2003. I have 2 porblems:
1 - I used AD to deploy Clients, but none of the client showed up as Assigned. I have to go to each client and run a discovery. Site gets discovered with no problem. MP working fine. ( I extended schema, SLP shows up fine in AD under system management) is there an easy way to assign without visiting every machine.
2- I published publisher 2003 for ADV/Client but when I checked log I found error 1603...etc is this a problem with the MSI? or problem with SMS 2003.
I am new to SMS 2003. I have 2 porblems:
1 - I used AD to deploy Clients, but none of the client showed up as Assigned. I have to go to each client and run a discovery. Site gets discovered with no problem. MP working fine. ( I extended schema, SLP shows up fine in AD under system management) is there an easy way to assign without visiting every machine.
2- I published publisher 2003 for ADV/Client but when I checked log I found error 1603...etc is this a problem with the MSI? or problem with SMS 2003.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
brenthunter2005
18 years ago
A return value of 1603 indicates that the MSI package had a fatal error.
Posted by:
Jase_T_Wolfe
18 years ago
Specifically, MSI error 1603 is "The file [2][3] is being held in use by the following process: Name: [4], Id: [5], Window Title: '[6]'.". The error messages are located in the Windows Installer Platform SDK.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.