Hi,
I've run into an issue with our exported Computer file structure causing ghost to crast when importing.
I've determine the root cause to the problem and a temporary workaround however this is not a solution.
We had a catastrophic failure on our ghost server after an upgrade in October 2019. After a clean rebuild we started exporting the tasks and computer structure on a regular basis weekly\bi-weekly basis. Our January export of the computers structure when imported crashes the console part way through. After manually digging around I’ve determined the problem to be 4 systems in different containers have no NIC listed. In the console it states that the NIC are disabled. In the exported file they are identified by having “<nics/>” which basically indicates no NIC.
<name>aaaTNTLIB-104</name>
<computer_name>aaaTNTLIB-104</computer_name>
<serial_num>CY09aaaa</serial_num>
<uuid>{4C4C4544-aaaa-3010-8039-C3C04F305132}</uuid>
<UAC>1</UAC>
<nics/>
<grouppath>
<group>aaaton</group>
<group>Tlib</group></grouppath></computer>
If I remove them from the exported file, it will import properly.
For now, I deleted those system from the console and they added themselves properly with their working NIC’s. Now the export file will import fine, however there is no dynamic group rule I could come up with to detect such systems before an export.
Has anyone run into this before?
Using Symantec Ghost Suite Ver3.3 R3 (Build 2642)
Running on MS Server 2016.
Thanks,
Ed White