@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.

@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.

Please close this ticket! It was my mistake. The issue was that I found a powershell script to disable the internet access during the MDT process, but the program was since fog tried to reach the ip address of the fog server, it was being blocked due to non internet access. I moved the script further down the process and it installed. Thanks for all of your input though.

I’m having issues with this, not sure what I’m doing wrong.
I’ll still troubleshoot, but getting this error:

Invoke-RestMethod : Cannot validate argument on parameter 'Uri'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command 
again.
At E:\Temp\Scripts\fogtest2.ps1:66 char:52
+          $TasktypesResult = Invoke-RestMethod -Uri $TasksURL -Method  ...
+                                                    ~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Invoke-RestMethod], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.InvokeRestMethodCommand
 
Invoke-RestMethod : The remote server returned an error: (501) Not Implemented.
At E:\Temp\Scripts\fogtest2.ps1:79 char:23
+ ... askResult = Invoke-RestMethod -Method Post -Uri $TaskURL -Headers $he ...

This is how I have it edited from the beginning, not sure if this messing it up:

$vmname =read-host "Enter the computer name you want to name"
$MacAddress = read-host "Enter the MAC Address of the host computer you're going to image"
$ImageName = read-host " Enter the name of the image you want to use"

I edited it like that because I want to test for example, another technician to just put the values in there and then your script will automate everything.

@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.

Please close this ticket! It was my mistake. The issue was that I found a powershell script to disable the internet access during the MDT process, but the program was since fog tried to reach the ip address of the fog server, it was being blocked due to non internet access. I moved the script further down the process and it installed. Thanks for all of your input though.

@Jamaal said in unable to install CA certificate (MDT 2013):

@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.

It was working before…

Which components exactly were used when it worked last? Windows 10, which build version? fog-client 0.11.16 I suppose? MDT 2013?? Just trying to rule out what we can here.

Ok, I’m using MDT 2013 update 2 and during building the reference image, I used Windows 10 build 1803. To be honest, I don’t remember the build of the fog client, just used the new MSI one, not the legacy one.

for some reason, I can’t get that error no more, but after looking in the logs of MDT, I get this: Application Fog - install returned an unexpected return code: 1603.
The version of the fog client is 0.11.16

@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.

It was working before…

Which components exactly were used when it worked last? Windows 10, which build version? fog-client 0.11.16 I suppose? MDT 2013?? Just trying to rule out what we can here.

Ok, I’m using MDT 2013 update 2 and during building the reference image, I used Windows 10 build 1803. To be honest, I don’t remember the build of the fog client, just used the new MSI one, not the legacy one.

@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.