We are running windows 7 professional, and are not going to update to windows 8, windows 10 maybe when it drops.
[quote=“Joseph Hales, post: 46729, member: 18131”]Windows 7 ultimate and Enterprise include bitlocker as well as windows 8 and 10.[/quote]
Unfortunately Bitlocker isn’t available for Windows 7 Pro, and we really don’t want to purchase it for all of our computers.
When connecting an already encrypted drive to a Windows Machine, the system immediately tells me: “You need to format the disk in drive X: before you can use it.” meaning the entire drive is encrypted.
Using DiskCryptor to mount the drive (and provided the correct encryption key) I can then view the drive as any other USB device.
In Windows Disk Management the drive is listed as RAW
The trouble is we image our machines to a base level, and then join them to the domain, and throw them on the shelf to sit until someone needs to swap out. And we want the ability to browse the entire drive, securely by using the application on our support systems.
The performance hit should be negligible as all that needs to be entered at power on, would be the decryption key and power on password.
So it’s really a question of, will it work? I’m encrypting a system now and will test with a Raw image upload onto Fog and try to restore.
I’ll provide an update when its done in a few hours.
He’s not to concerned about the same encryption key or phrase being used just so that we have an additional layer of security. A power on password only stops the laptop from getting powered on. Encrypting the drive (and our base image) would at least obscure the information on the drive. Preventing intellectual theft of anything on the system.
And since 99% of our staff have laptops, a baseline of encryption, that is uniform across the company is most easily managed using 1 encryption key or pass-phrase, albeit it’s less secure.
But the entire disk is / will be encrypted. Any more input?
We are looking to start encrypting our mobile employees, sales staff mostly (using DiskCrytor)
My Boss would like to expand this to be our standard, which I am all for, my question is, will the RAW format image properly pull all of the details needed so I can backup and restore equipment as it comes in or goes out?
Network boot does work from the local drive on the server.
It fails to work from the iSCSI drive though. We’ve copied, and confirmed the permissions, confirmed the drive settings Master and active etc.
It continually times out at TFTP. swapping the master drive back to the internal hard drive, imaging works. (within the fog storage node administration)
That is how we are trying to add the device.
It’s iscsi, we’ve been able to add it has a storage node, and set it as primary and active. But receive a TFTP timeout when we try to image a machine using it as the storage node.
You mean, move our entire fog server onto the iSCSI device as a hypervisor client?
Well we’ve considered it, but the trouble is, this device only works on Windows Server 2003, and Redhat 2 or something like that (officially).
Plus the device is pretty old having a total of 512 MB of RAM.
If you’d like to point me in the “right” direction I can look into it, and see if it’s worth it for us to try and do that. Just means we’d have to setup our ubuntu server, dhcp server, and fog server.
It wasn’t painful to do… but we really just wanted to initially use the device as a NAS device to store our images.
Lastly this entire unit has been setup in a private network, so we can get much higher imaging speeds from around 35 minutes, down to 4-6 minutes. (even running concurrent imaging)
OK guys,
I know it’s a recovery of an older thread, but I need some help.
We’ve got it that we can mount this iscsi drive on the ubuntu fog server, and even mount it within fog so we can configure it, load images to the share etc.
But we can’t get tftp to work for this share. Any help on what we’re missing would be great. Thanks in advance.
Additionally and this may be on a side note we are getting an alert “usbhid 2-1.6.3:1.1: couldn’t find an input interrupt endpoint” Now I believe this to be due to the KVM we are using. I’m fine with the alert, but is there anyway to get it to bypass this alert more quickly, as it is now it takes 2 maybe 3 minutes to get past this and either boot into fog, or image the machine.
I know a switch can have it’s “envelop pushed” a bit, but am curious as to how.
Anyways on a side note we’re finally getting started with that Promise device and will be testing with that on our private network soon enough.
Now if only I can get the boss to spring for some new equipment rather than the make it work equipment I’ve been using 
OK so just a general inquiry as I’m doing some testing and want to make sure it works.
So just tested and confirmed this, that enabling JUMBO Frames to 8000 does allow me to increase my throughput up to 3.57 - 4 GB per minute.
Is there anything else that I can do to get closer to 10GB/MIN?
What do you guys recommend.
This is built on a private network, I can do some testing here.
Most people would use an outside utility like Dell Diagnostics to perform a disk check before imaging a machine.
Which would avoid the fog-project from getting bogged down with software that not everyone might use.
A lot of interest, but no ideas…
Hrm…
It’s quite simple to get started with this.
If each machine is already loaded with a licensed copy of windows, you can easily image, and redeploy those images as needed.
If they are identical hardware the process is a bit more involved but easier to manage once setup. (this includes create several versions of “stock” images, Pre-SysPrep, Post SysPrep(system audit) and lastly an OOBE image.
Any time you want to update a machine you deploy the Pre-Sysprep image to 1 machine, apply any updates, and then upload that machine over the existing pre-sysprep image.
Run SysPrep and then upload this image over the existing sysprep image.
Then finally run an OOBE image (stopping before entering the product key, user name etc) and push this image to every machine you have.
Each time you deploy this updated image you can enter the windows product key, and user name and set it up as an OOBE (Out-Of-Box-Experience) computer, rejoin it to any network or domain you have, and you have the updates.
Still a good amount of work, but much better then running windows updates on 14 computers constantly.
Additionally the updated image can be scheduled to run on your end machines, meaning you can plan to have all of the machines ready to be setup with user and domain details when you come in the following day.
OK Guys here’s a new one for you, I hope.
I have a piece of hardware coming offline here soon, because our backbone runs windows everything. Servers, desktops, laptops etc and since we can no longer get support for Windows Server 2003.
We clearly use fog (since I’m posting here as our imaging tool of choice)
I would love to use this device as NAS for my images.
Has anyone else used this as NAS for their images
Now I know the device is compatible with RedHat and SuSE Linux, (windows server 2003), is there an easy way to determine if it’s compatible with Ubuntu for this purpose?
Some product information [url]http://firstweb.promise.com/support/file/manual/6_VTrak_M-Class_Product_v1.3.pdf[/url]
Does this apply to the entire image folder, or only specific images.
I meant a specific image, i realize I wasn’t specific.
Well every printer has to have drivers.
You simply need to find where CutePDF places them.
[SIZE=12px][FONT=Verdana][COLOR=#000000]%Program Files%\Acro Software\CutePDF Writer[/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#000000]Is a likely place where they would be put, additionally you can check the registry, the script I have will give you the path for the printers, check and see if CutePDF stores the drivers somewhere therein. [/COLOR][/FONT][/SIZE]
[SIZE=12px][FONT=Verdana][COLOR=#000000][/COLOR][/FONT][/SIZE]
Hrm,
So the local host, each time at startup is having the PDF printers deleted by the Fog Print Manager?
Is the software (pdf printer) built into your images, or are you selectively installing it?
I have a feeling you’d have to add the PDF printer as a localhost printer (on the Fog Printer Manager) but I haven’t had to do this yet, we use our domain controller as our print manager, and use GPO’s to deploy them out.