Peter33

You can put the Setup.iss in you package source path (same level as the executable) and just call "avsetup -s" The reason why they are using this path in the admin guide is here "avsetup.exe -a -r.". They did'nt define a capture path for the answer file with the "/f1" switch. In this case the answer file will be stored in %windir% by default. So for an admin guide this part is not very professional. Also the use of the "-a" switch is suspect. This switch is reserved for administrative installations and not for package installations. My Advice is to create a new answer file with "avsetup.exe -r -f1"c:\temp\setup.iss" (change the path to what you want). Copy the answer file to your package source and just run "avsetup -s" in your command line.

I don't see anything wrong in the command. SCCM was only appending the absolute path to the executable, but quotes are set in acorrect way. The only problem i see that the system has no access to the share. Has the Network Acccess Account a read access to the share?

The unattended.xml is specified in the "Apply Operating System" step.

Conclusion = The Setup wants an absolute path for the answer file ? This is a behaviaor i know from Oracle Client Setups but not from Install Shield Installers. If you name the answer file Setup.iss and call the Setup without the /f1 switch it should work though. The Setup.exe should be looking for a Setup.iss by itself. This neat little setup seems to be some kind of nightmare First thing i would try is to transform the whole thing into a Wise MSI. Unfortunately you don't have this opportunity.

You should only add NIC and Storage drivers to you PE image. Anyways, your error "Windows setup failed, code 31" is caused by a mismatch in your unattended.xml file. Did you create a new unattended.xml with WAIK for this operating system or did you just copy it from another windows setup?

You can do that by defining a variable in your script and give it a value of FALSE. On your cancel button just perform a self.close(). On the OK button action set the varibale to TRUE. Group everything behind the HTA in your task sequence and run this section only when the variable is TRUE. This way you don't have to care about leftovers on your hard disk.

Hi Bound, you can edit the MSI file to get rid of this launch condition. There is a free MSI editor named Orca. Get it and open the MSI file with, then go to the "LaunchCondition" preperty table and delete the entry. Save the MSI, and you are done. Edit: Hope you also did read what he was stating about the custom actions. "for a silent install. I still had to use an msi editor (installshield) to create a transform to remove two custom actions that were causing errors during the msi installtion: CheckLanguageUpdaterResult and CheckUpdateFeaturesResult. The application still installed correctly before removing those errors, I just needed to remove them so SCCM would not report a failed installation." Not sure if this can be done easily with Orca. I am using Wise Package Studio for MSI editing, but this is not a free product.

Have you seen this post in the Cisco Forums ?

OK, here is what the log says. Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming CustomAction CcmCreateIISVirtualDirectories returned actual error code 1603 MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory. <--- this is a popular error from SCCM 2007. Removing BITS - Reboot - Readd BITS helped there. Also you may have not all required IIS role features installed.

The drivers are not in te folder because they probably have been imported for a different model already. As long you activated them for your model category they will be applied to the driver package though. Drivers can only be imported once vor every version. Post the smts.log of your task sequence.

You posted only the Property Table dump of the MSI log. Without the complete log it's hard to tell where the problem is. I guess this is a secondary server installation? Make sure you have installed the the prerequisite features (.NET 3.5, BITS, Remote Differential Compression).

wmic COMPUTERSYSTEM GET AdminPasswordStatus 1 (0x1) Disabled 2 (0x2) Enabled 3 (0x3) Not Implemented 4 (0x4) Unknown

Maybe you forgot to switch the app to run as local system. Custom apps are running in the user context per default. Anyways, create an MST file for your MSI which copies the lic file to the correct location. This way you need only a single app.

Hi bound, sorry, i got the wrong error code from my memory. Just double checked it again. -3 maens "Required data not found in the Setup.iss file" I had such a case some month back, where the setup wanted to install a prerequisite, that had been already installed on the machine where the answer file was created. The setup came up with a dialog that was not captured and threw rhis error. The solution was to install the prereq program before the setup as single package.

It's an Install Shield error and means that the answer file has not been found. Did you quote the path of your answer file? You got a space in there. And why do you call the whole path at all? Is the file not in your package? Is suggest to put the whole command into cmd file and to run the cmd. pushd %~dp0 CiscoEmailSecurity-7-2-0-039.exe /s /v /qn /f1"w7x64unattend.iss" popd exit /b %errorlevel% Edit: Just to make sure. Did you create the answer file on a 64Bit machine?

Hi Folks, i'm facing the problem that i want to get rid of 2 service accounts (MIgration Users). But i can't delete them in the console, because this function is not implemented ( still not ... growl ). Is it save to delete them from the SQL table, or are there any cross references in other tables? Thanks in advance Peter

This might help you.

Actually i am doing the build and capture just with MDT2012 now on a VM with bridged network. Its DHCP but can be configured static too of courseOf course you have to import the base applications in MDT this way, but we have only 15 now, and you can refer to the SCCM Sources without copying them to the imaging machine. The VM gets booted with a PXE iso file. The benfit is that you can use the captured image with any other deployment type (like Ghost). It's also way faster than the SCCM Imaging.

There are several ways to achieve this. The easiest is to modify your unattended.xml (oobe section) file with WAIK. You can also use a command line step with "net user /add" command.

Before you try to install a secondary server make sure you meet all prerequisites. The Computer Account of the Secondary Server and of the Primary Server have to be members of the local Admin group of your new Secondary Server. If you want to use PXE Boot for OSD on the new server, add the Role "Windows Deployment Service". Then configure it, but without adding boot images. Add the following Features to the Server: BITS, Remote Differential Compression, .NET Framework 3.5.1. Enabel the inbound Rules for SQL Ports TCP 1433 and 4022 in your firewall. You should be fine and able to install the Secondary Server if these conditions are met.

You can perform a simple WMI Query fot the KB number like this ... select * from Win32_QuickFixEngineering Where HotFixID = "KB2533623" Just another query for further needed Hotfixes.

If you set it to always rerun it reruns according to your schedule. To be mentioned, "As soon as possible" is no valid schedule. Just set it your schedule to "at logon". Chances are good that program is not running then. To avoid a client spam create a negative collection with all clients that have not installed the program yet and apply the advertisement to this collection. As soon as the program is installed and the client runs a hardware inventory, the client object will be removed from the collection. That's what i do with all mandatory program upgrades.

Hi Wolfgang, you can do this with the MDT database. Have a look at this. Johan made an example for an MDT Deployment, but this should also work for the SCCM integration.

Just open a CMD and type "net helpmsg" followed by the error code. For custom error codes of some installers like SAPGUI you have to try your luck with google. Anyways some are just meaningless and not documented.

Why so complicated? Just run the installation from inside your script.