Auto Login/Net boot disk ???'s
Hi guys! Im the new guy here so I'll explain my current situation as best I can:
The gov agency I work for has been using Ghost for a couple years now in the forms of Multicasting and Bootable DVD's. This year I was tasked with evaluating a product from CA called Desktop DNA (this is not a sales pitch). Anyway, DDNA migrated a users settings/ data files based on filters and other crap. So getting this app to integrate with Ghost while using Software Delivery to push everyhting has taken quite a toll on me, but after the past couple months (of researching/working on this, while answering the phone and helping stupid users) I'm stuck on one simple problem.
BOOTING!
I've gotten copies of the Ghost Solutions Suite and the PowerQuest DeployCenter, using both the boot disk creator from Ghost, and the Virtual Boot Environment from PQ. The VBE is basically an .img file that is pushed (with a couple other support files) to the destination forcing a reboot and loading the img into RAM and booting from it...quite ingenious. But the Ghost boot disk's wont automatically login to our AD domain. Since I can use any boot disk availible and just use Winimage to create a floppy image of it I've tried Bart's disks, and a number of others with minimal success. I was told by Symantec tech support (what a bloody joke!) that I should use a batch file to process the login, that way I could use a normal network boot disk to autodetect my nic, hit the dhcp box for info....you know. But I am at a loss as to finding any info on using batches for that.
I really doubt that anyone else here has been forced into an environment like this, using almost 4 different products all together, but if anyone can throw me a bone onto either a newer boot disk, a home-grown one that works with AD or even some batch help I'd be much ablidged!
Thanks guys!!
The gov agency I work for has been using Ghost for a couple years now in the forms of Multicasting and Bootable DVD's. This year I was tasked with evaluating a product from CA called Desktop DNA (this is not a sales pitch). Anyway, DDNA migrated a users settings/ data files based on filters and other crap. So getting this app to integrate with Ghost while using Software Delivery to push everyhting has taken quite a toll on me, but after the past couple months (of researching/working on this, while answering the phone and helping stupid users) I'm stuck on one simple problem.
BOOTING!
I've gotten copies of the Ghost Solutions Suite and the PowerQuest DeployCenter, using both the boot disk creator from Ghost, and the Virtual Boot Environment from PQ. The VBE is basically an .img file that is pushed (with a couple other support files) to the destination forcing a reboot and loading the img into RAM and booting from it...quite ingenious. But the Ghost boot disk's wont automatically login to our AD domain. Since I can use any boot disk availible and just use Winimage to create a floppy image of it I've tried Bart's disks, and a number of others with minimal success. I was told by Symantec tech support (what a bloody joke!) that I should use a batch file to process the login, that way I could use a normal network boot disk to autodetect my nic, hit the dhcp box for info....you know. But I am at a loss as to finding any info on using batches for that.
I really doubt that anyone else here has been forced into an environment like this, using almost 4 different products all together, but if anyone can throw me a bone onto either a newer boot disk, a home-grown one that works with AD or even some batch help I'd be much ablidged!
Thanks guys!!
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
ST170SP1
19 years ago
Hi,
The image file you are currently sounds like it might be a PXE boot disk only loading UDP not a full TCP/IP Stack. You will need the full TCP/IP stack to authenticate and use network resources.
Working for an agency does that mean that all your machines are from the same OEM - therefore a finite number of NICs? That being the case it should be quite simple identifying the hardware and loading the IP drivers.
You say that you have used Barts disks have you tried the network boot disk at http://nu2.nu/bootdisk/network/? This uses PCI scan to enumerate the NIC and load the appropriate drivers.
With a full IP Stack you should then be able to do a NET USE to your network resource containing all your images.
Regards,
JamesT
The image file you are currently sounds like it might be a PXE boot disk only loading UDP not a full TCP/IP Stack. You will need the full TCP/IP stack to authenticate and use network resources.
Working for an agency does that mean that all your machines are from the same OEM - therefore a finite number of NICs? That being the case it should be quite simple identifying the hardware and loading the IP drivers.
You say that you have used Barts disks have you tried the network boot disk at http://nu2.nu/bootdisk/network/? This uses PCI scan to enumerate the NIC and load the appropriate drivers.
With a full IP Stack you should then be able to do a NET USE to your network resource containing all your images.
Regards,
JamesT
Posted by:
c0ckbl0cker
19 years ago
JamesT, Thats for the reply. Well if Im using a PXE disk then my Ghost is ALL screwed up. Like I said I tried using a Network Ghost boot disk, the Network share disk from the PQ DeployCenter, and yeah Bart's modular boot disk. As for the nics yup, your right their pretty much limited to Broadcom 100/1000's, 3c905x's and I'll usually throw in the older Intel 10/100 for giggles. Getting these disks to find the correct nic has not been a problem yet, it's just getting authenticated thats kicking my a$$. I thought about trying to remove the "logging in" part of one of these disks, and just "net use" ing the share providing my share credentials. I mean I cant see any reason why I should have to be authenticated to the DC. Currently when we start a session manually we always log in as local admin anyway then provide our domain acct info to access the share...works everytime. And on these disks I've tried using the FQDN, like:
username domain
domain\username domain.xy.se.army.mil
domain\username domain
But I always get an access denied error, with the ghost disks it's specifically an Error 2202.
username domain
domain\username domain.xy.se.army.mil
domain\username domain
But I always get an access denied error, with the ghost disks it's specifically an Error 2202.
Posted by:
ST170SP1
19 years ago
Mapping drives from WINPE using an unauthenticated user id and passing the domain credentials is what I do! Then I use Ghost etc to do image maintenance.
Have you got any restrictions on your shares to only allow authenticated machines?
What does you NET USE command look like? (suppress anything that is not public!)
Regards,
JamesT
Have you got any restrictions on your shares to only allow authenticated machines?
What does you NET USE command look like? (suppress anything that is not public!)
Regards,
JamesT
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.