@Sebastian-Roth said in unable to install CA certificate (MDT 2013):
@Jamaal said in unable to install CA certificate (MDT 2013):
I changed from the quiet switch to passive and I noticed the CA certificate error.
Please give us more information about this. Exact error message? Possible take a screenshot and port here.
I’ll take a screen shot when I get back home, but the message says exactly unable to install CA certificate during the install via MDT
Hello, all,
I’m having issues installing the fog client with MDT 2013 deployment during a reference build on Windows 10 build 1803 & 1809. It was working before, but I was getting an error message via MSI 1603. I changed from the quiet switch to passive and I noticed the CA certificate error.
I tried doing a reset cert I saw online as a command for fog, but no go. The fog build is 1.5.5. I also tried both IP address and fqdn of the server.
Any suggestions would be appreciated. If I install via the command prompt manually, it works fine.
@george1421 what version of MDT are you running btw? I’m on 8450.
@george1421 Ok, for some reason when I see the status page that the deployment is complete, it’s not going to the desktop as you stated. It’s rebooting if I put the FINALACTION=REBOOT or if it’s blank, it reboots. If it’s on SHUTDOWN, it shuts down.
@george1421 I’ll try when I get home in a few. When I closed the display page trying to do this, the VM shuts down, but I’ll try again, think I’m missing something. I’ll let you know.
@george1421 Ok, that’s where I’m getting stuck at. So I took your recommendation to change the skip summary to no so I get the dialogue box, but how do I get to the Windows logon console? I can do for example f8 to get the command prompt, but I want to get a Windows console to run the final script like your setup for example.
My bad I didn’t write all the info.
@george1421 Well I just want to have MDT 2013 to be at a state for me to run final scripts so I can run my own
sysprep and copy the unattend.xml to the panther directory. Now I was following this from Johan putting this as the final task and it’s not running in Winpe mode.
Can you please tell me how you get to run a script after deployment without rebooting and triggering the dirty environment in MDT 2013? I tried following this post from deployment research, but no matter what I try, it won’t go back into Windows, stays in Winpe and I get the dirty environment message:
I just want to do final touches without having to rerun syysprep, know what I mean?
I just want to see what’s easier to maintain, ex fog client vs using sed command. Where it says computer name, do I replace it with a computer name I want to start? Ex NY-WB- is what I would like to start as a prefix
George, I’m 90% good with deployment. I was able to get a working script to deploy the Lenovo drivers. I saw how to use deploy bug to see where it was failing.I ended up using an older script you put. So here’s my issues.
@george1421 ok, now I understand. I just made that change. I had it set on no because I was following deployment research website. I’m going to try that approach. I’ll post up some updates when I get everything accomplished. Thanks again for guiding me through this.
@george1421 I’m a little confused, sorry. Should I remove the task from MDT to not sysprep the machine and run a custom script to sysprep & use a custom unattend.xml? I have these in the bottom of my rules page, not sure where to see the closing status message.
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=YES
SkipBitLocker=YES
SkipSummary=YES
SkipRoles=YES
SkipCapture=NO
SkipFinalSummary=YES
@george1421 or should I let the VM boot after MDT deployment, create a cmd script to sysprep again and also point the setupcomplete.cmd and unattended.xml to their correct spots?
@george1421 George, I started playing around with the copy script and worked good copying to the Windows 10 client, but I didn’t do fog as yet. I just booted the VM after MDT to test it out and got through setupcomplete.cmd to copy over, but looks like the unattend.xml didn’t make the changes. Any ideas? I didn’t see the c:\drivers folder create even though I used WSIM to add the line? Do I need to call the command to create the folder drivers as well?
@george1421 hey George, so I see what the problem was with WSUS. I thought the content folder can be put anywhere since it said remote path. I tried my NAS both network path and iscsi, but still locks up the downloads. I did research and said it’s not supported in a network share, so I put it back on the local.
Now for the Office 2013 updates, I found this online to extract the service pack 1 and I was able to get the updates faster compared to WSUS.
https://www.howto-outlook.com/howto/slipstreamoffice2013sp.htm
I’m working on the unattend file and will work on copying files this weekend. The offline script I was following sucked and didn’t work no matter what I tried. I’ll keep you posted. Thanks for leading me in the right direction.
@george1421 and when I get to this process on copying files, where should I tell Fog to copy the unattend.xml? Into c:\windows\system32\sysprep? Or the panther folder?
@george1421 ok, I’m gonna try that route for the updates. Just curious, what classifications do you use in WSUS for Windows 10? I selected Windows 10 and windows 10 updates and latest build I think, don’t remember.
@george1421 said in Help with Win10 Driver injection:
.\DeploymentShare\Scripts\client\DeploymentShare\Scripts\client\update.bat
yea it’s driving me nuts here, lol. The reason I was gonna go this route was because for some reason, the WSUS is taking forever to download the updates. I let it run for a few hours and I also noticed some errors in WSUS it was trying to download Office 2013 Service pack 1. Would you know on how to speed that process? I have Server 2012 R2 and tried things like increasing the Application Pool that I saw online on IIS. I’ll play around with the offline again shortly as well.
George,
Not sure if you’ve done this with MDT, but I’m having issues using WSUS Offline updates for Windows 10 Ver 1709. I got a reference from IT Bros, but still errors out when updating with updates. https://theitbros.com/integrate-wsus-updater-with-mdt-2013-to-deploy-windows-10/
I even tried looking at the YouTube link, but still fails, won’t run Windows Offline install, but will mount the drive with no issues. Do you know another way?
@george1421 lol, yea sometimes I slip a few more questions last minute 
ok, I heard of them and I’ll start working on things. I’ll reply back in a few days or so letting you know how I made out. Thanks again for your help.