Deployment Solution

Hello everyone.

I've been trying to get a simple deployment solution to work for quite a while yet.

After clearing a lot of hurdles, I've hit a roadblock I have no idea how to solve. Right now, I install Windows ADK, create a configuration with Bootwiz, edit the startup.bat to mount a pair of additional network drives and map a costum static IP to a machine. Everything works great, and it connects to the server just fine. Even receives commands and deployment tasks.

The problem is that it only boots into automation if I run the automation folder installer. Everytime I run it, it prompts me to reboot my computer, which it happily does without further input and proceeds to load Windows PE. But when I return to production, the automation folder doesn't show up on MSCONFIG. It doesn't appear in the boot menu. And when I send a task to the client that requires booting to automation, it fails to do so. 

I've seen two odd things so far. A few days ago, when I couldn't even connect to the server, the installer would create a hidden "boot" folder in C:\ where the wim file was placed along with what I think is a costum bootmng. Now, after the automation installer runs, the folder isn't created. It still boots to automation, but I have no idea what's happening and allowing it to so.

Secondly, when I do boot into automation, I used to be able to see two extra drives. C: would be a 100 mb with a bootmng for windows, while D: would be the normal C: drive I get in production. Windows PE would boot into X:. But right now, C: is a 300 mb drive called "BOOTWORKS". It seems to be the "embedded partition" because Windows PE still boots into X:, the RAM temoporary disk. I can't see the other two drives anymore.

I have no clue about what changed this. It seems it's ditching the "automation folder" and going back to "automation partition" from previous versions, but I'm still using GSS 6.8 as far as I can tell. I tried searching the forum since I've previously found solutions for all other problems, but I didn't see anyone with this problem.

Oh, I might also add, in case other people see this, Anti-Virus software might be the biggest obsctale into creating an automation folder/partition.

I have no idea why. If I had to guess, anti-virus block DISM from acessing a lot of files needed to create the automation folder. This leads to bluescreens (0xc000024c error) and other abnormailities. I don't really have a choice to suspend the anti-virus (company policy) so I had to use another computer to create the automation folder installer. I feel that symantec should really mention somewhere on the documentation that Anti-virus software really messes with it, because bootwiz doesn't really give you any indication that something went seriously wrong.

One other thing I can't find in the documentation:

When I'm creating the automation installer, I get 3 options. "Automation", "Network" and "Stand-Alone".
I couldn't find a document clarifying what each of these do. Can someone give me a quick rundown? Tried them all so far, didn't really see diferences.

Koriath,

I am not sure what would be removing the automation folder... I would take a look at the below documentation and make sure everything is being configured correctly and then test from there.

Ghost Solution Suite Automation Folder User Guide

Koriath,

Please mark the most relevant post as the answer if the issue has been resolved.

Not exactly what I wanted, but got me on the right path to find a solution. Thanks.