Hello,

I was viewing a powershell script I saw online about 2 days ago and I got it to add the new machine in the fog server with the MAC address fine. I also saw how to add 1 or more snapins if needed, so thank you for that.

Here’s my question. So is there a powershell command to select adding the Active Directory option to the new host instead of going to the console to check off for each new host?

I know how to do it in the console, but want to know how to do it in this script I saw on the forum by ScottyBullet: https://forums.fogproject.org/topic/11183/api-create-host-deploy-task-error-invalid-tasking-type-passed/7?_=1590872437608

So I’m basically putting the Powershell script together when the other techs put in the valid info in Microsoft Orchestrator, it will kick off the powershell script, add the machine to the fog database and kick off imaging while plugged into the network.

Appreciate all the hard work on this forum. I’ve learned a lot on here and imaged a lot of computers from last year.

George,

How did this work for you? I’m thinking about doing this as I’m starting to run out of room on a hyper v box and thinking about just building a Windows Server 2019 vm and make it as a secondary storage server.

@Sebastian-Roth said in API - Create Host Deploy Task "error": "Invalid tasking type passed":

@Jamaal From the error message I would imagine that this last call is failing because an earlier query also failed and variables are not being set correctly because of the earlier error. So you need to post the full error you see!

I am not a PowerShell wiz but from what I know the read-host stuff you added should work.

Thanks man, you pointed me in the right direction.
So I went back to your script again and ran it and noticed it kept giving an error message after the 1st throw command, like Powershell was skipping the 2nd and 3rd throw command.

What I had to do was do a read-host, but kept the $ (read-host “enter machine name”) for example:

[String] $MachineName = $( read-host “Provide the target machines Name”),
[String] $MacAddress = $(Read-Host “Provide the target machine Address”),
[String] $ImageName = $(read-host “Provide the Image Name to assign to the new target host”)
So I saw the task in the task list right away. I’m so so with powershell and starting to get better with it, you know. What I would like to do is maybe figure out powershell commands to add the snapins as a read-host so the tech can select which snapins to use instead of going to the Fog console to be more automatic.

And I would like Powershell to start the task once the hostname is added to Fog. I can start playing around that.

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.

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

https://deploymentresearch.com/Research/Post/427/Final-Configuration-for-MDT-2013-Lite-Touch-now-with-Autologon-support

@george1421

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:

https://deploymentresearch.com/Research/Post/427/Final-Configuration-for-MDT-2013-Lite-Touch-now-with-Autologon-support

I just want to do final touches without having to rerun syysprep, know what I mean?

@george1421

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

@george1421

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.

• I used the fog client and joined the domain successfully, this is windows 10 build 1709. I saw last min where you said to add the pinstall command in the setup complete.exe to install the drivers. How do I use the sed command to copy another setupcomplete.cmd from the fog server instead of reimagining? I looked at some examples, wanted to test using the sed command to copy the updated unattend.xml and setupcomplete.exe, but not sure where to put it in for example, fog.ad file. I get syntax errors.

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