I've been beating my head vs a wall for a while now(4 months on and off) and I'm wondering if someone has already found a solution to my problem or if there is no solution.
Before we used Ghost 7.5 and we were able to pull an image and deploy it with no problems. Upgraded to 8.0 Corperate and now images can be pulled and deployed same as before, except that the clones will not join the domain.
What happens is they get the image, go through the windows setup and then the appear like they have joined the domain. They will reboot(unknown period before they do) and when they come back up they are no longer joined. At that point they are 'finished' and I am able to join by hand and it will then be done.
IIRC, I am able to use boot disks(and name the machine manually) and it joins the domain correctly. Unfortinuetly that is not an acceptable solution on the whole. I need the abilty to set up the task and walk away knowing it will be done correctly.(save for the standard check-up)
I still need to try a solution listed on Symantec's website still but I doubt that will work.(Pull unjoined image, deploy. Pull deployed image and use that as finished)
I've tried several things, pulling the image joined, not joined and no success yet. I've even heard that it might have something to do with paritions.(we have a diagnostic parition we need on the image) I still have several things to try over the process several more weeks so it will be a bit before this gets resolved. But again, I want to know if someone has run into this problem before and if they have solved it.(And hopefully the solution.
Oh, I am also aware of 'net dom' but considering that required 3 reboots seperate from the imaging process that is not my prefered solution. Well, that and I'm not sure we have the tool.
Thank you in advance,
Twinmoon
Before we used Ghost 7.5 and we were able to pull an image and deploy it with no problems. Upgraded to 8.0 Corperate and now images can be pulled and deployed same as before, except that the clones will not join the domain.
What happens is they get the image, go through the windows setup and then the appear like they have joined the domain. They will reboot(unknown period before they do) and when they come back up they are no longer joined. At that point they are 'finished' and I am able to join by hand and it will then be done.
IIRC, I am able to use boot disks(and name the machine manually) and it joins the domain correctly. Unfortinuetly that is not an acceptable solution on the whole. I need the abilty to set up the task and walk away knowing it will be done correctly.(save for the standard check-up)
I still need to try a solution listed on Symantec's website still but I doubt that will work.(Pull unjoined image, deploy. Pull deployed image and use that as finished)
I've tried several things, pulling the image joined, not joined and no success yet. I've even heard that it might have something to do with paritions.(we have a diagnostic parition we need on the image) I still have several things to try over the process several more weeks so it will be a bit before this gets resolved. But again, I want to know if someone has run into this problem before and if they have solved it.(And hopefully the solution.
Oh, I am also aware of 'net dom' but considering that required 3 reboots seperate from the imaging process that is not my prefered solution. Well, that and I'm not sure we have the tool.
Thank you in advance,
Twinmoon