wmmayms

Okay, next thing you need to check is that your computer is found.. look into your smspxe.log (\SMS_CCM\Logs). Open up this log and reboot your client into F12. Then search the log for it´s mac adress or UUID. Make sure you find a row saying somethign similare to this: <![LOG[GetBootAction: MAC:00:50:56:81:14:B7 SMBIOS: SMSID:GUID:D304F6CF-C408-46F6-9F98-B1D0E5F9DA5C LastAdv:]LOG]!><time="16:27:30.097+-60" date="01-10-2012" component="smspxe" context="" type="0" thread="4204" file="database.cpp:661"> <![LOG[Advertisement results: OfferId:T0120002 OfferTime:10/01/2012 16:26:00 PackageID:C0100023 BootImageID:C0100014 PackageVer: PackagePath:\\xxxxxxxxxxx\SMSPXEIMAGES$\SMSPKG\C0100004\ Mandatory:0]LOG]!><time="16:27:30.097+-60" date="01-10-2012" component="smspxe" context="" type="0" thread="4204" file="database.cpp:734"> <![LOG[ProcessDatabaseReply: Found optional advertisement(s): T0120022]LOG]!><time="16:27:30.098+-60" date="01-10-2012" component="smspxe" context="" type="0" thread="4204" file="pxehandler.cpp:491">

It is suppose to look like that. You need to press F12 twice because you did not set a mandatory schedule in your advertisement.

that error is actually good for you It means you have contact! Try restarting the wds service once. If it does not help, update your boot image (new source version). And make sure you have booth x86 and x64 deployed to your DP (muchos importante!)

Looks like all you need to do is change your MSSQL service to use a domain account. You can do this from services.msc

try installing WDS manually, configure it. Reboot and then remove the wds again and then let SCCM have a try. And if you are using DHCP options remember to specify booth of these: Options 66: 10.0.0.10 Options 67: SMSBoot\x64\wdsnbp.com Oh and yet again, try using delayed startup for the WDS service. I have seen this do miracles in my lab env more then once

In 2012 you don´t need to install the WDS manually, just make your DP a PXE point and it will handle everything :-) If you have problem with a hanging wds service I generally recommend people to try setting it to delayed startup.. "In my eventlog i could still see the error that WDSIMGSRV could not be initalized. Do i need this component?" - i get this error to, don´t worry about it :-)

run: msconfig

Try these wrappers If they don´t work check your media..and then run the scripts without silentflagg to see if the setup is prompting a specifik error.. PS: I know it was hell getting this to work properly.. Install.vbs: On Error Resume Next Set oShell = CreateObject("WScript.Shell") Set ofso = CreateObject("Scripting.FileSystemObject") strWinDir = oShell.ExpandEnvironmentStrings("%SYSTEMROOT%") sDest = oShell.ExpandEnvironmentStrings("%ALLUSERSPROFILE%") & "\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2008" strUserAppDir = oShell.ExpandEnvironmentStrings("%LOCALAPPDATA%") oShell.CurrentDirectory = oFSO.GetParentFolderName(Wscript.ScriptFullName) scriptpath=oShell.CurrentDirectory + "\" App1="""" & scriptpath & "setup.exe" & """" &" /Q /IACCEPTSQLSERVERLICENSETERMS /ACTION=install /features=ssms /HIDECONSOLE" App2="" RunnApp1 = oShell.Run(App1, 1, true) 'RunnApp2 = oShell.Run(App2, 1, true) strShortcut = sDest & "\Configuration Tools\SQL Server Installation Center.LNK" ' msgbox strShortcut If ofso.FileExists(strShortcut) Then ofso.DeleteFile(strShortcut) If ofso.FolderExists(sDest) Then ofso.DeleteFolder(sDest) If ofso.FolderExists(sDest) Then ofso.DeleteFolder(sDest) wscript.quit 0 uninstall.vbs: On Error Resume Next Set oShell = CreateObject("WScript.Shell") Set ofso = CreateObject("Scripting.FileSystemObject") strWinDir = oShell.ExpandEnvironmentStrings("%SYSTEMROOT%") strUserAppDir = oShell.ExpandEnvironmentStrings("%LOCALAPPDATA%") oShell.CurrentDirectory = oFSO.GetParentFolderName(Wscript.ScriptFullName) scriptpath=oShell.CurrentDirectory + "\" App1="""" & scriptpath & "setup.exe" & """" &" /Q /IACCEPTSQLSERVERLICENSETERMS /ACTION=uninstall /features=ssms /HIDECONSOLE" App2="MsiExec.exe /X {4AB6A079-178B-4144-B21F-4D1AE71666A2} /qb" App3="MsiExec.exe /X {3A9FC03D-C685-4831-94CF-4EDFD3749497} /qb" App4="""C:\Windows\Microsoft.NET\Framework\v2.0.50727\Microsoft Report Viewer Redistributable 2008 (KB971119)\install.exe""" & " /qu" RunnApp1 = oShell.Run(App1, 1, true) RunnApp2 = oShell.Run(App2, 1, true) RunnApp3 = oShell.Run(App3, 1, true) RunnApp4 = oShell.Run(App4, 1, true) wscript.quit 0

Im using this command line successfully: setup.exe /Q /IACCEPTSQLSERVERLICENSETERMS /ACTION=install /features=ssms /HIDECONSOLE This will only install the management studio though =)

Never tried any tool for this. I have done a few smal changes but then i have edited the xml files with notepad. What are you looking to do?

Best way is to start testing the product. The basic things are done through wizards so start of with that and then advance as you move along. All you need is a single virtual server and a virtual client.

I agree! Enjoy.. would have been nice to be on site.. but ya..

Open a program under a package in sccm. On the enviroment tab make sure "program can run:" is set to "only when a user is logged on" On the advanced tab make sure "When this program is assigned to a computer:" is set to "run once for every user who logs on"

MSI+advertised shortcuts. If you want to do it through SCCM then you can have a program run for each user that logs on. In you program you could use regedit /s <regfile> to import your settings.

For the time being i would recommend VB scripting.. If you ask me the same question next year i would proberbly say Powershell =) Java is the wrong path if you are administering windows clients.

You could use "select case" or you could join the view v_gs_operatingsystem (note im offline atm so name might not be 100%)

When using SUP with SCCM you should not specify any GPO settings for WSUS.

Hm i just found a similare problem with the customer im working at atm.. I created a customized IE9 installation with IEAK. Everything seems good, TS is running fine etc..All is fine until a user tries to logon.. then they recive: The User Profile Service failed the logon. User profile cannot be loaded. And they are then thrown back out to ctrl-alt-del Problem was solved by removing the customized IEAK9 package and deploying a new clean package..

MDT is a toolkit just for deploying operating system.. SCCM is used for alot more then just deploying operating systems (application dist, software updates, inventory etc). It depends on your needs.. But for a smal organization MDT is golden

Begin with enabling F8 mode and look into your logs: cd %temp%\smsts

Im guessing your using "wsim" to build your unattended.xml? I don´t use it very much but you should be able to add a run once key (default user) in there somewhere.. [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings] "MigrateProxy"=dword:00000001 "ProxyEnable"=dword:00000001 "ProxyHttp1.1"=dword:00000000 "ProxyServer"="http://ProxyServername:80" "ProxyOverride"="<local>" GL, and when you have some time... Look into Microsoft MDT, it´s free, much easier and alot more powerfull http://www.microsoft.com/download/en/details.aspx?id=25175

Hm you can do this with GPO. Or you can customize the IE installation with a tool called IEAK. http://technet.microsoft.com/en-us/ie/bb219517

Before digging to deep into the code you should look into MDT just like Peter said. Depending on your needs it might save you some time :-) PS: here is a cool tool for customizing the wizards: http://deploymentbunny.com/2011/05/26/modifying-the-lite-touch-wizard-in-mdt-2010-sample-2/

If you don´t see all your active directory groups then there is a problem with your discovery settings (system group discovery). Make sure you are targeting the correct path.