denmyos

I don't get this!!! When I capture a reference computer that has all windows updates installed, shouldn't it also capture the updates.?? When i deploy the captured image i have disable all windows updates in my TS, because its already installed on the reference/captures computer/image. But when I deploy my captured Image there are no updates on it, and I have to do the updates all over again.??!! This can't be right.?? Can anyone please direct me to a wetsite/tutorial that people know works and is using them selfs. apparently I'm to stupid to getting this to work my self.!!

This is my customsettins.ini [settings] Priority=CSettings, CPackages, CApps, CAdmins, CRoles, Locations, LSettings, LPackages, LApps, LAdmins, LRoles, MMSettings, MMPackages, MMApps, MMAdmins, MMRoles, RSettings, RPackages, RApps, RAdmins, Default Properties=MyCustomProperty [Default] OSInstall=Y _SMSTSORGNAME=Naestved Hovedbibliotek SkipCapture=NO DoCapture=YES ;ComputerBackupLocation=\\DeploymentShare$\Captures BackupFile=#year(now) & Right(String(2, "0") & month(now), 2) & Right(String(2, "0") & day(now), 2) & "-" & Right(String(2, "0") & hour(now), 2) & Right(String(2, "0") & minute(now), 2)#.wim SkipBDDWelcome=YES SkipAppsOnUpgrade=YES SkipUserData=YES SkipAdminPassword=YES SkipProductKey=YES SkipBitLocker=YES SkipBitLockerDetails=YES SkipSummary=YES SkipFinalSummary=NO SkipComputername=YES OSDComputerName=PC-001 JoinWorkgroup=HB_BIB SkipDomainMembership=YES ApplyGPOPack = NO UserLocaleAndLang = da-DK,da-DK KeyboardLocale = 0406:00000406 UserLocale = da-DK UILanguage = da-DK KeyboardLocale=da-DK SkipLocaleSelection=YES TimeZone=105 SkipTimeZone=YES TimeZoneName=Romance Standard Time SkipPackageDisplay=YES LanguagePacks001={d626d423-f370-4764-9e69-48049b62635e} SLShareDynamicLogging=\\mdtserver\deploymentshare$\%OSDComputerName%\ Exlude Browser Choice WUMU_ExcludeKB1=976002

Sorry but i'm still struggling with this. Is there a log fil where i can see if MDT actually capture my updates, when it captured my image.?

Finally I ended up with a capture.wim but this error turned up at the ended.?

Still not working. The "add user" is my bad. But it still won't capture from a deploy TS. I have to look at it again tomorrow.

At this very minut I'm trying to capture a new way (possible the right way...) Where I use a deploy TS and in the deploy wizard I tell to capture and give it a path for the capture.wim. Before, I would just deploy and in the deploy wizard I would ignore the capture part, and only deploy. Have to wait to see how it goes. @jaminben I can see that you have a OSDcomputername=REFERENCE How does that work.? I rename my computers each at a time after they are deployed. Thanks for all the help. edit: My new way of capture didt'n work. It's just deployed, but did not capture anything. But change the "rules" to SkipCapture=NO DoCapture=YES Trying again now, and see how it goes.

In short, I'm capture it this way. But I'm in a workgroup, so I don't get the same error. https://www.youtube.com/watch?v=8grZMM1byWg I will return later with screen dumb of my TS. Thanks for your help. @jaminben Is your "regfix for browser choice" a fix to delete the icon on the desktop? @snagrat Yes, the Image I capture is the same I deploy. So all the updates should be on that Image when I deploy it, unless I'm doing something really wrong. I have only being doing mdt for a couple of months, so I'm still a newbie. This is my deploy TS My capture TS

I build a virtuelt reference image, with all windows 7 updates installed on it. But when I capture the Image via MDT (BDD_autorun.wsf) and deploy the image again, there are no windows updates, and the newly deployed Image needs to spend another 3 hours updating. What i'm I missing here, do I do something wrong.?

I need to deploy my image with two scripts, which I can't get to work.First I need to have a automatic login for my default user. (netplwiz) I'm running this script, with changes thats fits my needs. The passwords needs to be blank so the user don't need to login, (it's a library, and a "kiosk" computer) But for some reason its not working, nothing is happening, the batch (I made it into a batch file) is executed with no errors, but the is no change in the login.? REG ADD "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v AutoAdminLogon /t REG_SZ /d 1 /f REG ADD "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultDomainName /t REG_SZ /d HB_BIB /f REG ADD "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultUserName /t REG_SZ /d "Naestved Bibliotek" /f REG ADD "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultPassword /t REG_SZ /d (needs to be blank) /f With my other script I'm trying to get the passwords for my user "Naestved Bibliotek" to never expire Net user "Naestved Bibliotek" /add passwordreq:no /active:yes /passwordchg:no /expires:never But I don't get a tick in "password never expires" any help would be appreciated PS: I'm in a workgroup PPS: It seems that I can get auto logon to work when i write a password,, BUT I need to get it to work WITHOUT a password..

I'm deploying some Lenovo m78 (10BS-S02P00) for some reason Lenovo is giving me a crap load of drivers that I don't need, even when you download the correct Sccm driver package for the 10BS-S02P00 it gives you a huge amount of drives I don't need. What is you best pratices to control the amount of drives in your MDT?

Why would that tiny little thing cause such a big problem.?

I think i finally found the culprit. When you do a task sequence it ask for full name, two days ago i start write Næstved, instead of Naestved, which i have been doing prior to that. writing naestved seems deploy smoothly. I still dont know what Full name is for i dont see it anywhere in the OS.

I have no idea what going on now. I thought it was the product key, but now i get the same error without the product key. I think it has something to do with the boot.wim, as you said, but i can't figure out what.!? Is it correct that the correct boot.wim is in deploymentshare\boot\litetouchpe_x86.wim When pxeboot i get a choice from Lite touch windows PE (x86) Lite touch windows PE (x64) I press the x86 and the boot proccess starts BUT the it uses a boot\x86\image\relaxwinpe.wim is this correct.? Something is really wrong here I use a x86 boot, when i get to the "windows Deployment wizard" AND choose the x64 TS i have made for my win7 x64 image,,it works!!! I forgot to mention I'm on vmware 10 workstation.

yes, i doubled checked.

Nope didn't work, but it should be best pratice to do a full, when importing a new image. But i'm wondering why doing but its loading a relaxwinpe.wim instead of a litetouchwinpe.? hmmm it seems like the product key is the culprit, when i use the product key and copy+past it in "specify the product key for this opreation system" (which i have done many times before) I get the error in my first post. But if i do not use a product key i get no error, and the deployment goes through as normal.

If I get the boot file from deploymentshare->boot After importing a OS into MDT, wouldn't that be the lastet bootfile.?

I decided to start from scratch again just to get a clean slate, so i delete all my image, TS. etc. Imported OS into MDT, made TS, imported image into wds and started to deploy, and now i get this error. I have been getting that error for two says now. Done everything, delete images in mdt,wds, delete TS and imported everything again, made new TS, imported in wds,,,,,and im still getting the same error. The weird thing is that, im only getting it with x86, NOT with a x64 images. The image is not corrupt, I installed it on a stand alone client, and it works fine. Its probably something simple that i over looked, but what.?

My machines are in a workgroup and get there updates from microsoft online server (not a wsus) It would be really great if i could update my computes doing deployment via the ZTIWindowsUpdate.wsf, but er several fail attempts. My command line look like this cscript.exe "%SCRIPTROOT%\ZTIWindowsUpdate.wsf" Start in \\servername\deploymentshare$\scripts\ My deployment works fine, but i get no updates. Is it even possible to it to work in a workgroup with no wsus.?

Is it a captured image? Are you sure it's not the sysprep administrator?

Solved!! My bad, wrong ip address etc Now its gettin weird,, I'm suddenly getting the same error from within my vmware environment.?? Other problem with psysical client still persist.!

We just did option 67 But still get TFTP. PXE-t04: Access violation DASH-E36: Error received from TFTP server DASH-M0F: Exiting option ROM we will try this solution And see what happens Look at the VMware virtual switch and whatever switch it is connected to, is there any form of broadcast filtering or prevention switched on, if there is everything but the initial PXE and DHCP (if it is on the same VM) would work but the those two require reception of a broadcast from the client, you may need to turn on a DHCP helper address or something in your external switch to convert those broadcasts into unicasts so that they get through. Just learned that our switches are Distribution Cisco 3750 Access HP A5120 I just installed wireshark on the vmware server,, it seems like the pxeboot is getting through.?

My server 2012 r/MDT/WDS is virtuel + clients (where pxeboot works) (on the same virtuel vmware as the server) 1 physical client (that can't pxeboot) is turned off. I will check with my network administrator.

I will check with the men wiser that me.

Mine is sat to bridged But since a physical win 7 can ping and get to the netshare boot\x86\wdsnbp.com.... it should work.

server 2012 r2 yes it does. The is actually a switch asking Domain or standalone.