CPS_TECH_DTAFT

Well as far as the group policies goes it is not affecting any of the current machines that have not been imaged. (NOTE* All machines have the configmgr client to include un-imaged machines) The only time this is occuring is post OSD. It really has me baffled. I will collect the logs this afternoon and append them to a post.

Well that isn't the case as we do not have a license agreement for Office 2007. And I have no other MS Office software packages setup beside the Office 2003. So far I have a completely backwards solution to the problem in that I have now setup a role requiring office to be installed. So after the image restores and it reboots and installs. The configmgr client will than pull down the office and reinstall it. But once the machine reboots it is uninstalled again and the circle continues. This is not a solution. I need to find out why Office is uninstalling. Odly enough I have checked all the logs on the Client and the Server regarding the machines that are doing it and I can not find any reference to the uninstallation of office. Also this did not happen in my test enviroment. It only started once I began to deploy to the rooms. I would not put it past myself to have checked the wrong logs. Or to have missed the correct ones. So any suggestions would be greatly appreciated.

Well no real explanation needed. I have Microsoft Office 2003 installed on our image using our Volume License Key. Post OSD after minisetup completes the machine comes up and it uninstalls office and it looks like a TS. The actual message is Installing Office. Once it completes it comes to the login screen I login and Office has been uninstalled. I do not have any Install Software Task sequences setup in my OSD.

There is another way of doing this in your task sequence and it may work better. Create a wsf script named Software.wsf <job id="Software"> <script language="VBScript" src="ZTIUtility.vbs"/> <script language="VBScript"> '//---------------------------------------------------------------------------- '// '// Global constant and variable declarations '// '//---------------------------------------------------------------------------- Option Explicit Dim iRetVal Dim sSoftInstallFolder Dim sFile DIM sScriptRoot Dim env Set env = CreateObject("Microsoft.SMS.TSEnvironment") sScriptRoot = env("ScriptRoot") sSoftInstallFolder = "c:\windows\temp\" '//---------------------------------------------------------------------------- '// End declarations '//---------------------------------------------------------------------------- '//---------------------------------------------------------------------------- '// Main routine '//---------------------------------------------------------------------------- On Error Resume Next iRetVal = ZTIProcess ProcessResults iRetVal On Error Goto 0 Function ZTIProcess() On Error Resume Next iRetVal = Success ZTIProcess = iRetval '//---------------------------------------------------------------------------- '// Copy Post script to disk, Update RunOnce and change login settings. '//---------------------------------------------------------------------------- For Each sFile in Array("Install.vbs") If oFSO.FileExists(sScriptRoot & "\" & sFile) then oLogging.CreateEntry "Copying " & sScriptRoot & "\" & sFile & " to " & sSoftInstallFolder & sFile, LogTypeInfo oFSO.CopyFile sScriptRoot & "\" & sFile, sSoftInstallFolder & sFile, true Else oLogging.CreateEntry "Unable to copy script " & sFile & " from " & sScriptRoot & " because it does not exist.", LogTypeInfo End If Next oLogging.CreateEntry oUtility.ScriptName & " COMPLETED. Return Value = " & iRetVal, LogTypeInfo End Function </script> </job> Than Create a vbs file named Install.vbs Set oShell = CreateObject("WScript.Shell") Set oFso = CreateObject("Scripting.FileSystemObject") If oFso.FileExists("C:\MySoftwareInstaller.exe") Then oShell.Run "C:\MySoftwareInstaller.exe /s",0,true End If Place bolth files in your MDT Toolkit Scripts folder. In your TS use the toolkit run command line: cscript.exe "%ScriptRoot%\Software.wsf" This is one way of modifying the script and idea documented here: http://kongkuba1.spaces.live.com/?_c11_BlogPart_BlogPart=blogview&_c=BlogPart&partqs=cat%3dDrivers

Not sure if you guys are still confused or not. But in summary to what he said Verify Package Can Be Installed Without an Advertisement. Open the program properties for your package. Go to the advanced tab Check "Allow this program to be installed from the Install Software task sequence..." Click Apply than OK Update Distribution Point Now look at your package while on the Packages Node. Write down your "Package ID" and the EXACT name of your program. Asumming you are using the default Install Software. The variable it uses is PACKAGES. So open up the collection that contains your computer. Or create one and Add a membership for your computer. Next right click on the collection. E.G. "All Systems" or "All Unknown Computers" select "Modify Collection Settings" Click on the "Collection Variables" tab. Click on the starburst icon. Ok now the name is going to be our varible from our Install Software action plus three numbers in sequence. So the name will be. PACKAGES001 , PACKAGES002, PACKAGES003, and so on you get the idea. So your first software package lets say is firefox and its Package ID is W0100017 its program name is Silent Install Name = PACKAGES001 VALUE = W0100017:Silent Install Click ok, and your next package would be PACKAGES002, and so on. Hope that is pretty much crystal clear.

I would like to seperate the 'Setup Windows and ConfigMgr' Action. From the documentation I can find the only thing I can find that this combined action does is call -cscript at the ZTIConfigure.wsf -Initiate a Reboot so MiniSetup Can run -Post MiniSetup: Execute as Local System CCMSetup.exe..... I would test this but I am not currently at work. If this is correct I should Simply go into my OSD TS Create a SubGroup 'Setup Windows [MiniSetup]' ( In the old 'Setup Windows and ConfigMgr' spot ) -Setup Toolkit Package -Run Command Line: [ cscript.exe "%ScriptRoot%\ZTIConfigure.wsf" ] -Restart Computer: [ The currently installed default operating system ] [ Uncheck Notify User ] Than I could simply add the ConfigMgr Package to my Install Software action. This is all from memory so please correct me if I am wrong. Thoughts, ideas much appreciated. Thank you, Daniel Taft

My Little Disclaimer: If this information is elsewhere in the forums, I could not find it using the search function. Feel free to correct me. I have been for a couple days now prepping our SCCM server and have now with success completely configured it and all our application packages. All is successfull from boot media and pxe. Now my final task to make the process complete remote for our enterprise. As this is a new system in our network. None of our computers currently have the configmgr client installed. Is this client required for a remote deployment. I have created the mandatory advertisements and computer associations for the labs and rooms. But nothing happens; However, bolth pxe and boot media work. In final I guess my question is what are the requirements for a Remote Deployment in an Enterprise with vlan sub-division.

Also I just relized this is in the wrong section could an admin/mod move this to the correct forum subsection. Thanks.

Also "jamitupya" recommendation was spot on. For one reason or another it didn't propagate my DP's when I first updated them. But now I have another problem. The details below show the information relating to the PXE boot request for this computer. Please provide these details is to your Windows Deployment Services Administrator so that this request can be approved. Pending Request ID: 334 After updating my DP's I now get this issue. NOTE* This is still with my test computer sitting right next to the PXE server on the same network/VLAN Well I have helpers set up in my cisco switches for the DHCP server, as a side note right now I am using DHCP options 66 and 67 not helpers to point the traffic to the PXE server. But I have not looked into that yet as I can not get a computer working that is in the same vlan/network as the pxe server. So ip helpers would not cause this as there is no need to route the traffic up the tier to reach the destination.

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your Windows installation disc and restart your computer. 2. Choose your language settings, and then click "Next ." 3. Click "Repair your computer." If you do not have this disc please contact your system administrator or computer manufacturer for assistance. File: \Boot\BCD Status: 0xc000000f Info: An error occurred while attempting to read the boot configuration data. I have tried everything in this forum among many other attempts. Everything was working fine when I had WDS and DHCP running on the same server But I need them to be separate. I have since disabled the WDS on the DHCP server. Grabbed an extra server we had. Performed a clean install of Server 2008, installed all applicable roles, MDT2010, SCCM 2007, SQL 2008, etc... And I have everything configured properly. I setup options 66 and 67 on the DHCP server and I get this problem. I have taken my test pc out of its vlan placed it in the same vlan with my DHCP and WDS servers. Still didn't help I have checked the logs and didn't see any errors. Also our network consists of 12 VLANS, over a 1000 computers, and I have to have this working before the Christmas break as I have been tasked out to perform a reinstall on approximately 600 computers. Any and all help would be greatly appreciated.