Error Code 1603

Why is it so hard to push good .Net patches?

Few readers need to be told that the Internet is a dangerous place. Anyone in the IT field knows that viruses, spam and malicious websites exist. Knowledge of these attacks and vulnerabilities has been the domain of specialized security gurus just a few years ago. But the need to understand computer security has spread beyond the domain of specialists. Today, even the IT end-users should be aware of threats and countermeasures against a certain degree.

By focusing on the plane instead of the disaster helps to ensure that you can survive the challenges that you have never considered. This guide business planning continuity offers a checklist to help analyze threats to appoint a team of crisis management, and develop a dynamic plan. Use it to simplify the planning and adjust to suit your business needs.

Most organizations small and medium businesses find the implementation of unified communications a daunting task, between the lack of internal expertise and the complex issues of integration, it is easy to back burner project. Using consultants with experience at an affordable price and seamlessly migrate your infrastructure to Microsoft Exchange 2010, SharePoint Lync and may be the way to take communication to the next level.

WSE 3.0 Silent push /Windows XP

Hey guys, I come here alot to check out the latest headlines and basically just to poke around, I signed up today because i am in need of a little help.

I am trying to rollout WSE 3.0 runtime and im getting the typical :
    "msiexec exited on x.x.x.x with error code 1603."

Im using this : PSEXEC \\x.x.x.x msiexec /q /i c:\some_app.msi

I can install this locally, however, it needs to get installed on about 800 systems.

Anyone here have success with this package?

Just thinking out loud...
Hmmm, not sure about using an IP address... ;) You might have a syntax error. I use this in a batch file (as an example for you):
psexec \\machinename c:\windows\system32\msiexec.exe /unregister

This will use PSExec on the LOCAL machine to run the msiexec on the REMOTE machine (\\machinename) to unregister the WI Service. I also use the full path to the msiexec.

If your path has any white spaces in it you should put it in double quotes.

You could also add an MSI log file (/l*v c:\temp\some_app.msi) then look at the full paths to see what is causing the 1603.

You might have a permissions problem too.

Professional Microsoft SQL Server 2008 Administration

Annotated code of Nebraska, a hand-book of the Nebraska decisions containing: I. The code of civil procedure. II. The Criminal code, including the code of criminal procedure. With full annotations and notes citing the official state reports, Federal and U. S. Supreme court, and Northwestern reporters; the American decisions, American reports, and American state reports, and Lawyers' reports annotated

United States Code 2006, Supplement 3

Southern reporter

West's decennial digest