Peter33

Well, in this case you might consider to use the MDT database feature of MDT2012 to assign computer names.

If you want to use the MAC Address as the computer name you could use this line in the default section of your customsettings.ini file. You could also tweak this a little bit more by replacing the PC prefix for Laptops. OSDComputerName=PC#Replace("%MacAddress001%",":","")#

Seems like you have created the activateWindows.bat.txt with notepad and forgot to remove the ".txt" extension. Downloaded file from http://HEG-36.ge-em....Windows.bat.txt to C:\_SMSTaskSequence\Packages\HEG00014\activateWindows.bat.txt InstallSoftware 16.05.2012 16:13:58 1040 (0x0410) Failed to execute command line '.\activateWindows.bat' .

Hi, this is what you log says ... TPM found in the following state: Enabled - False You need to enable the TPM chipset in the BIOS first. The way to apply this setting is different for every hardware vendor. So which hardware are you using?

Yep, you are right. Wise package studio got canceled right after we upgraded from 7 to 8 last year. I was pretty angry because we paid a lot of money for the enterprise licenses without having any information about the end of life of the product.

Sorry, my fault. Adobe only supports Adobe X for SCUP. There was a catalog for adobe 9 available 2 years ago. But it's gone now. Think that was just some sort of test and we also never used it. I prefered the script wrapper. for updating version 9. An AIP is and administrative msi installation (msiexec /a) where you can directly apply all needed msp files. Make sure that you don't apply security updates to it or it will break the installation and no further patches can be applied. Here are 2 links. http://blogs.adobe.c..._tai/archives/9 http://helpx.adobe.c...t-reader-7.html For every quarterly update you have to modify the base package/application and to update your distribution points. This way new installations are always being installed (almost) fully patched. You need an additional package that will update the already deployed installations with the latest patch. Of course you could also create a completely new package for every new single patch. A script wrapper which uses a wmi query to verify the installed version is useful though. Saves a lot of unneeded errors. Thinking about Eswars post again ... you also could abuse the application and supersedence model though, because scripts are allowed where msp files are not. But Adobe 9 would not be a good candidate for that. It needs a ton of patches. I would use it only for major versions.

Updates are not covered by the application model and by supersedence. This works only for msi files/major versions. Best practice for Adobe 9 is still AIP for new installations, which should only include the quarterly updates. Already deplyoed installations will be patched by the msp files, either by SCUP or by a package which holds all msp files and a script which installs the needed updates step by step.

Sorry, but there is no converter of even a good converter at all. Wise package studio has a function for that, but allows you only to convert Microsoft or Install Shield Exe installers. And it only works in 10-20 Percent of the cases. If you have an exe that can't be bothered to run unattended, you need to snapshot the installation. But try to avaoid that if possible.

Not to forget the coolest new feature, the deployment database, which gives you endless opportunities to tweak your deployments. There was a nice brakout session held at the MMS 2012 two weeks ago introducing all the new features of MDT 2012. Many thanks to Johan Arwidmark, who was a speaker there. Enjoyed all his sessions.

Well, is this the only advertisement that does'nt work? Do you have successfully deployed any other packages to your clients already? You should check your client agents settings and the boundaries.

Did you assign a schedule to make it mandatory for the clients?

No Problem. Here is a short powershell script which checks an SQL database for the License and performs the installation if a free key was found. ################################################# # Define SQL Login Credentials and Connection Details here $Server = "SQLSERVER" $Database = "DATABASE" $Username = "USERNAME" $Password = "PASSWORD" $Connect = New-Object System.Data.SqlClient.SqlConnection("Data Source=$Server; Initial Catalog=$Database; User Id=$Username; Password=$Password;") $Connect.Open() $Hostname = $Env:COMPUTERNAME.toUpper() $ExitCode = 0 # Let's see if we can connect to the Database if($Connect.State -eq "open"){ # Great. Now let's check if the Hostname has a License assigned already $cmd = $Connect.CreateCommand() $cmd.CommandText = "SELECT License From Licenses1 Where Client='$Hostname'" $Result = $cmd.ExecuteReader() If($Result.Read()){ Write-Host "Hostname Found In Database. Using Assigned License." $License = $Result.GetValue(0) $Result.Close() } Else { $Result.Close() # No Problem. Maybe we can find a free License. Write-Host "Hostname Not Found In Database. Checking For Free Licenses." $cmd.CommandText = "SELECT TOP 1 License From Licenses1 Where Client Is NULL" $Result = $cmd.ExecuteReader() If($Result.Read()){ Write-Host "Using Free License From Database." $License = $Result.GetValue(0) $Result.Close() #Whoop Dee Doo. We got a free License. Let's block and use it. $cmd.CommandText = "UPDATE Licenses1 SET Client='$Hostname' Where License='$License'" $retcode = $cmd.ExecuteNonQuery() If($retcode -eq 1){ Write-Host "Assigned License to Host." } Else { # What the heck just happened here! Write-Host "Failed To Write Changes To Database" } } Else { $Result.Close() # Shit happens. Let's buy some more Licenses and try again. Write-Host "Error: No Free Licenses in Database." $ExitCode = 2279 # Your Own Error Code Here [Environment]::Exit($ExitCode) } } $installParameters = "/i MSINAME.msi TRANSFORMS=MSTNAME.mst REBOOT=ReallySuppress SERIALNUMBER=$License /norestart /qn" $Connect.Close() $ExitCode = (Start-Process -FilePath "msiexec.exe" -ArgumentList $installParameters -Wait -Passthru).ExitCode If ( $ExitCode -eq 3010 ) { $ExitCode = 0 } If ( $ExitCode -eq 0 ) { Write-Host "Success: Finished Installation with Return Code 0" } Else { Write-Host "Error: Aborted Installation with Return Code $ExitCode" } } Else { # Must be Patch Day or something like that Write-Host "No Connection To SQL-Server" $ExitCode = 2277 # Your Own Error Code Here } Write-Host ".... I'm done. Let's exit now." [Environment]::Exit($ExitCode)

Well, that's bad. Sounds like the side by side assemblies are kinda messed up. Maybe caused by a snapshot installation. We had also 2 machines where the tool didn't work. Ended up with a reimaging because i did'nt want to waste to many time on it.

Try running this tool manually on the faulty system.

Actually you can enable this by editing the sms_def.mof in the section "Environment". Set everything to TRUE in this section. This will give you a new attribute class "Environment" for your queries. Edit: My fault. I thought you meant Environment variables.

You can use this query to see who made changes to your advertisements. select stat.*, ins.*, att1.*, stat.Time from SMS_StatusMessage as stat left join SMS_StatMsgInsStrings as ins on stat.RecordID = ins.RecordID left join SMS_StatMsgAttributes as att1 on stat.RecordID = att1.RecordID where stat.MessageType = 768 and stat.MessageID = 30008 and stat.Time >= ##PRM:SMS_StatusMessage.Time## order by stat.Time desc

For the storage device you need the driver from this path E5520-win7-A04-XW8PX\E5520\win7\x86\storage. Make sure that your driver package contains this one. Also mark the checkbox for unsigned drivers in the apply driver package step. If the driver is already in your Optiplex package just run "auto apply drivers".

MIF files are sms staus files, generated by "msiexec /m". Actually i never use this switch, because several manufacturers do not fill the property table of their msi's correctly, which is essential for a working MIF.

Lenovo is storing the Model name in the Win32_ComputerSystemProduct class. Check this out.

Rather use the class SMS_InstalledSoftware. They are the same on both systems, and you don't have to query two classes.

You can expand your query with the Win32_OperatinggSystem class. Take a look at the OperatingSystemSKU property. It will give you all the informations that you need.

Seems like you did not create a valid package for the SCCM client. No content source files for P0100009 Failed to resolve package source "P0100009"

Just create 2 custom collections for each language pack you want to deploy. The first one should hold the client names. In the second one create a query for the installed software, in your case Office XX, and link the query to the first collection. After your office installation force a hardware inventory on your client, so the second collection is going to be filled.

Use the portable version and create a custom msi file, or just use robocopy to copy the program folder. Or even more elgant, use 7zip to create a self extracting exe file (easiest method for programs like this).

If you create a custom task sequence, you can add a 'run command line' step. In ther you can chose the package path and place the setup line in the command window. The options tab of the command line step has a list of success codes, that can be expanded. Just add 255 to the string. A script wrapper would look like this in your case. Save it as vbscript file in your package source, and replace the installation command by 'cscript scriptname.vbs'. Set sho = Wscript.CreateObject("Wscript.Shell") strCommand = "Setup.exe /UL1033 /V'SERIALNUMBER=XXXX-XXXX-XXXX-XXXX-XXXX-XXXX'" intRet = sho.run(strCommand,0,True) If intRet = 3010 Or intRet = 255 Then intRet = 0 End If wscript.quit(intRet)