Archive for category Computer Forensics and Imaging
This post is using the Symantec Solution Suite 2.5
I’m setting it up so that I have the ghost client installed on the majority of our workstations. The only ones I’m not installing it on our encrypted laptops. The first problem I came across was it getting stuck at “Polling for bound server.” I found that means the NIC drivers for my computer aren’t in the WinPE PreOS. So I found the drivers for my card and popped open the ghost boot wizard. Even after adding the NIC driver I couldn’t get the damn thing to work and could not find where it would tell me what the problem was. It was my own fault. I discovered the error at the top by double clicking on the failed job in the ghost console, which brings up the event log and it always failed on “To Virtual Partition.” I didn’t realize I could then click on that and the specific error would pop up. That error up above means the SATA drivers for my board weren’t in WinPE either. After going to the motherboard manufacturer’s website to get them and adding them through the steps below, it is now creating my image of my test computer.
Any missing drivers will need to be the Vista 32-bit version. It doesn’t matter what OS your computer is running.
Open the ghost boot wizard to edit the Windows PE PreOS. Then on the second screen click on WinPE-512 and click copy. The 512 image is for machines that have over 512mb of memory. Name it whatever you want. You don’t want to go editing the original copy of it in case it gets messed up somehow.
Now go ahead and click edit on the image you named. Depending on which drivers you are updating, select the proper tab and add new driver.
After finding the path for the driver and giving it a descriptive name make sure you check the box for Vista as the OS.
Sometimes it doesn’t actually add the drivers to the image the first time you hit OK on the top two images. So click edit one more time and scroll down the list for the drivers you added to make sure their boxes are selected. It takes a few minutes for it to update the image.
Any computers that you have already installed the ghost client on need to have the virtual partition changed to the version you just created. In the ghost console right-click on them, go to the client tab and select the correct one from the drop down list. After changing that on all of your machines you’ll then need to run a task that refreshes the configuration and inventory on all the computers. THEN the backup regime or image create task will work. If you want all the new computers you install the ghost client on to use the same version of WinPE then go to the tools menu in the ghost console, down to options and change it on the client tab there.
Oh, in the midst of troubleshooting these problems I tried the PC-DOS virtual partition, but ended up getting stuck in a boot loop that kept sending me back to it and not letting me go back to Windows. The second article below describes how to hide the ghost partition to fix that.
My Dad came to me asking me if I could crack a password for a word document he was trying to edit. He had created a form template and needed to edit it but could not remember the password he used. If all you have is a password set to disable editing of a word document it is pretty easy to remove it.
- Open the file and save as html file
- Open the html file in notepad or similar text editor
- Look for and delete two lines
The UnprotectPassword will be a random combination of letters and numbers, depending on what the password to the document is.
- Save the file.
- Now you can open it in word, you may see an error. But the file will open and you can now edit it. So now re-save it as whatever file extension you want and you are good to go.
Doing this messed up the page size settings of the document, but that is easy to fix. It saved my Dad from having to recreate the document from scratch.
This is using Ghost Solution Suite 2.5, which is ghost 11.5, to image a hard drive that is encrypted by PGP encryption. But there is a good chance these same steps will work with other encryption software.
If you want to bypass all my troubleshooting that it took for me to get this to work then click here to go straight to the solution.
July 5, 2011
This adventure began late last week. I need to figure out how to image our encrypted hard drives in a manner that keeps the encryption intact. I’m not going to wait hours for a drive to decrypt just so I can image it and then have it spend another few hours, or however long, to re-encrypt it. The plan is to get this to work so that I can pull an image of each of our laptops every time we have huge software changes. I’m not sure what’s going to qualify as large enough changes to make me go through this, but I’ll figure it out when I get there. After I get this process to work properly I’ll just use the ghost client on the machines to back up the user files every 2 weeks or so.
Well last week I started my experiment with ghosting one of our unused encrypted laptops. It took me forever to realize that I can’t use the windows client to pull or push an image because ghost doesn’t like that I have to enter the password before the computer will finish booting up. Even though I was standing at the laptop when the client forced a reboot and typed the password in right when it prompted for it, it wouldn’t go into the WindowsPE environment. I thought I was being too slow at first, but that wasn’t the case.
I created a boot disk with the right NIC drivers on it for these laptops and had it boot to the CD. I finally got it imaging and then noticed it was splitting the image into the default 2GB chunks. With these laptops being 500GBs, that just isn’t going to work. I kept thinking of spanning, not splitting, so it then took me awhile to find the correct switch to add to the settings /facepalm. I finally got it to pull the image, it took 4 or 5 hours to do it and the next day I turned around and pushed the image back out to it – I’m using the ghostcast server on one of my servers since I don’t have a large enough external hard drive for a 500GB image and I don’t feel like buying one right now.
I came in this morning and rebooted the machine to see if the image worked. Well it prompted me for my encryption password but then it won’t boot into windows so I need to run the repair command. But I can’t do that until I decrypt the drive because the repair boot disk won’t see the hard drive until I do. So now I get to yank the hard drive out and hook it up to another laptop in order to decrypt it, that will take 12-24 hrs.
But, there is one more thing I will try before I become stumped. I used the split=0 switch, but not the switch to force a sector-by-sector copy (-ia). I thought I read in the documentation or in their forum that it would detect whether it needed to be sector-by-sector, but I don’t know how to find out and it didn’t work. The last time I had to decrypt a drive by hooking it up to another laptop as an external it took at least 20 hrs to finish. I’ll start that process shortly and try to image it again tomorrow.
If anybody has any advice please feel free to share it.
To be continued….
Well I tried imaging it again after waiting 20 hrs for it to decrypt, then 20 more hours for it to encrypt itself again. The image failed. I tried using both the -split=0 and -ia switches and did see an error where it was saying something about -split=0 not being used properly or whatever. So now I have to decrypt it again (20 hrs), run the fixboot command, and let it encrypt itself again (20 hrs). Then I will try imaging one more time only using the -ia switch for sector-by-sector copy. I will report back once this has been attempted. I will figure this out, damn it.
October 11, 2011
So 3 months have past since I last spent much time trying to figure this out. I’m too stubborn to admit defeat and let something like this go without exhausting all resources first. I just knew there had to be a way to get it to work. I came across a KB article on Symantec’s website that sounded like exactly what I needed to do. Why this was never mentioned in any forum posts about PGP (or encryption in general) and Symantec Ghost (that I found anyway) is beyond me. I only ever saw mention of sector-by-sector copying and if you read my original post, then you know how well that worked out. I just realized the new article that I found also refers to the -IR switch, which is a raw disk image, as sector-by-sector. What the hell? Let’s be a little more confusing please /sarcasm.
- Use a ghost boot CD or usb drive to get into the WindowsPE environment.
- After it boots up and pops the Ghost GUI up, close that so you’re at the black command prompt.
- From here I had to go back a couple directories by typing cd.. to find the directory the ghost executable lives in. I think it’s Ghost32.exe.
- The switches you need to use are -IR, -FRO, and -SPLIT=0. So type ghost32.exe -IR -FRO -SPLIT=0 and hit enter. Now go through the normal steps to select the disk to image and the place to save it.
You are going to need a removable hard drive or the ability to ghostcast from a server that has enough space for the image to be the entire size of the hard disk, even if the disk only has 50GB of information on it. Since the image is a raw disk image (the -IR switch) it is imaging the entire disk. You can use the -SPLIT switch to chop the image into smaller bits, but that doesn’t make the image any easier to manage with hard disks being so large these days. Unless you need to chop the image into files that will fit on DVDs or Blu-Rays, I don’t see that being useful. Or maybe you have small usb hard drives to split the image onto, I suppose that’s helpful.
I pulled an image and turned around and pushed it back out and it worked perfectly. I rebooted the laptop this afternoon and it was like nothing happened – encryption and everything is intact. It looks like, based off the switch descriptions linked below, that the only difference between raw disk image and sector-by-sector is that the raw disk image ignores the partition table. Funny how the KB article still refers to it as sector-by-sector, yet their own switch description page does not.
I was given the task of trying to figure out how to boot a spanned DD image file as a virtual machine in the software of my choice. It was an old image of a Windows 2000 machine that was spanned in 650MB blocks, a total of 10 files. I originally tried converting each segment into the VirtualBox VDI file just to see if I could get something usable, but that wasn’t successful. I looked online for 40-45 minutes trying to figure out how to merge all the segments into one file. I had no luck at all with that, but I did get another idea because of a previous assignment in this class (computer forensics).
What I ended up doing was mounting the spanned image on my machine as another “disk” on my computer. I then used ProDiscover Basic to capture an image of the “disk” – essentially capturing an image of an image. I then used Virtualbox’s command line tool to convert the new DD image file into their virtual hard drive file, a VDI.
Software used: Mount Image Pro, ProDiscover Basic, and VirtualBox. Mount Image Pro is only a trial version, but it will work perfectly for this. This is meant for students of my class who already have access to a demo version of ProDiscover Basic. There may be free alternatives out there that can do the same thing and can probably be swapped out easily for those steps.
Here are my steps, with lovely screenshots.
Open Mount Image Pro, click the mount button, click on add image. Browse to where your image is located and select the first file in the span and click open.
After you click on the Mount Disk button a window will pop up where you can select some options. The only way I got this to work was telling it to mount as physical and logical. I left the other 3 options as default.
After it has mounted you may see in the window that there are multiple partitions.You’ll want to pay attention to the As column and in this case, the one called PHYSICALDRIVE2 in my example.
Now open ProDiscover Basic, cancel the prompt to start a new case if that comes up, go to the action menu and click on capture image. In this box you’ll want to select PHYSICALDRIVE2 as the source drive, choose the destination to save the file, and most importantly, choose the UNIX style DD format. Click OK and walk away for a few minutes while it captures the image.
After the image has been captured the next step is to use the VirtualBox command line tool to convert it into a VDI file. I find this to be easiest if you move or copy the DD file into your VirtualBox program files directory (C:\Program Files\Oracle\VirtualBox is the default path). If you don’t put the file in that directory you’ll have to type out the entire path so the tool knows what file to convert.
Open a command prompt. Change the directory so you are in your VirtualBox installation directory by typing:
cd c:\program files\oracle\virtualbox
Now comes the command to convert the file into VDI format.
vboxmanage convertfromraw filename.dd newfilename.vdi
Hit enter and let it do its thing. Once it returns a blank line it’s done.
Now you can cut and paste the DD and the VDI files into whatever directory you want. Open VirtualBox and go through the prompts to create a new machine like you would any other time. Instead of having VirtualBox create a new disk you’ll just tell it to use an existing disk and choose the VDI file.
The migration from 7.5 to 11 was not as smooth as I had hoped. We used to netboot and ghostcast that way but with this new version I would have had to edit all the config files and I am not willing to put in the time to figure out how to do that when I’ve never attempted something like that before. So I opted for the boot CD, which wasn’t the easiest thing in the world to come by either.
Our newest machines are Dell Optiplex 755’s. I was able to find a forum online where someone posted directions on how to make the boot disk for it with the correct NIC drivers. It worked perfectly, I was finally able to ghostcast.
1. I went to Dell’s support site (support.dell.com) and downloaded the Intel drivers (about 5MB). Or you can download them here; ftp://ftp.us.dell.com/network/R162323.EXE2. Extracted the contents to a new folder3. Located the DOSNDIS2 directory. Within there there should be 2 files (e1000.dos and protocol.ini).4. Created a new file called oemsetup.inf5. Edit the oemsetup.inf file and copy/paste the following into it.; OEMSETUP.INF for Broadcom Ethernet Adapter[netcard]
E1000$=”Intel Ethernet”, 0, NDIS, Ethernet, REAL, E1000$_ini, E1000$_ini[E1000$_ini]
NETDIR=5:E1000$.dos6. Save the file7. Run the Symantec Ghost Boot Wizard Creator.8. When asked to Select the Network Driver choose Add9. Click the Setup Button and point to the NDIS folder you just created.10. Everything else is default until the end.
Now I’ve hit another snag; we dual boot linux-windows and now linux won’t boot up. I can’t get it to boot up into anything because I’m using the linux bootloader. It’s stuck with GRUB in the upper left corner of the screen. I thought ghost was supposed to work with linux. Anybody know what to do?
Update: I just reinstalled grub and it works perfectly now. Sweet.