 |
Frequently Asked Questions
Q Where do I install my ImageCast program?
A You can install the ImageCast program on any workstation running NT 4.0 or Windows 95 within the same network segment as your model machine and your target clients you want to clone. After you have booted you model machine with your client diskette (you can build your client diskette using the client builder part of the program) and you have highlighted the client you want to make your image file from then click the “create” button on the controller. ImageCast will ask you where you want to store your image. The image creation begins. After your image file is finished you boot up the computers you want to clone to with the client diskette and establish the network connection between them and the controller. Highlight the image file, highlight the target client(s) and hit copy.
Q The ImageCast installation stops for no apparent reason and my system seems to slow down to a crawl. Why?
A This is caused by a conflict with resident/running virus software. Exit or disable all virus software during ImageCast installation. It is also a good idea to exit all other programs on your system prior to running ImageCast Setup.
Q My systems have different network cards. I am multicasting an image of Windows 95 or NT to all of them. How will each system get set up properly?
A After the image is on each client system you must go around to each of them that has a different network card than the original and set them up accordingly.
Q Do I need to have TCP/IP enabled over the entire network to multicast?
A No. You simply add the TCP/IP network stack to the Windows 95 or Windows NT system that has been designated as the controller, map to the server (if any) you’d like to store the images, build the multicast client diskettes similar to the image that exists in the \Client\MClient directory (click here for detailed instructions), and you are set. When you create an image of one of the Client systems you simply use the Browse button in the Controller to select where you wish to save the image (local drive/directory or network drive/directory), hit the Create button in the Controller and enter a filename. ImageCast will take over from there.
Q My systems have different video cards. How does ImageCast handle this?
A ImageCast puts an identical image of the model system on each client system. If you have different video boards it is best to set up the model system to use a default video driver such as 640x480 or 800x600. After the image file is transferred, you can change the video mode/drivers on individual workstations as needed.
Q In general, how are all of the customized settings for Client workstations handled by ImageCast?
A ImageCast puts an identical image of the model system on each Client system. Therefore, you must go around to each workstation and put in any customization necessary, such as: 1) station name, 2) primary domain, 3) IP address if not auto assigned on your network, 4) video drivers, if different from model, 5) configure network card, if different from model, 6) etc... Future versions of ImageCast will integrate custom settings more gracefully.
Q Does ImageCast run under Windows NT ?
A Yes it does. It is designed for Windows 95 and NT 4.0 or higher.
Q I downloaded the trial version of ImageCast and cannot unzip it. I get a message that it won't run under DOS. I’m running DOS ver 6.22\Novell 3.12. My company uses DOS to move system images back and forth to the server. How can we run this program using DOS?
A The file is meant to be installed on either Windows 95 or NT. Once installed, you can grab the Client-appropriate files (the help walks you through building a Client disk) and build your DOS-bootable Clients. The main feature of ImageCast is the ability to multicast. This mode of operation requires the Controller, which runs on Windows95/NT and is installed using the file you mentioned. However, if you are used to the pull (Standalone Client) mode used by some competing products you can also build DOS-bootable disks for that mode which do not require the Controller or any other Windows system to be on the network. You still have to have a Windows-based machine to get the files out of the installation program.
Q If you have a 4 gig drive and a 1gig image to be copied to it, does the drive remain a bootable drive?
A Yes.
Q Can ImageCast image a Novell server?
A Yes, but destination server must be booted to a Client diskette first.
Q How large of a drive can Image Cast handle? 4 gig? 9 gig?
A We have imaged up to 6 GB drives. It should work with up to 8.4 GB drives, questions remain when going above that level with IDE. In theory, the software is capable of a 24 GB drive, but not tested.
Q Will ImageCast overcome DOS, older versions of Windows 95 and old UNIX partition limit of 2 GB/ 8 GB?
A No. Whatever the limitations of the operating systems are will remain the same.
Q What are the average image transfer times to be expected with ImageCast?
A Transfer times will depend on the operation and the hardware being used. Throughput bottlenecks can occur anywhere from the hard drive to the network. There are many different scenarios possible but here is an example:
File compression 44%
Image creation & upload 18:38
Image download 7:44
Image download to 25 clients 10:34
The model system had 179 MB of data on a 210 MB Hard Drive. 10-Base-T Ethernet, 75 MHz Pentium Clients.
Q What amount of compression can I expect on an image?
A Between 40% and 55%, on average, depending on the data in the image.
Q Can we make images to or from SCSI drives?
A Yes, you can create an image from a SCSI drive assuming you are casting to a SCSI drive.
Q My Serial number doesn’t seem to work
A Go to the directory where you installed ImageCast and open the text file names serial. It will give you the right serial number for the version of ImageCast you have.
Q I have Compaq Deskpro 4000 computers and I am having difficulty getting the client diskette to boot.
A Go to Compaq’s website and download a file named movepci.sys. In the file config.sys on the client diskette make sure the DEVICE=MOVEPCI.SYS instead of himem.sys.
Q How does ImageCast handle partitions?
A ImageCast dynamically resizes restored partitions to maximize the capacity of the target drive. That means if the target drive is larger than the drive the image file was created from, any leftover space will be available. If you attempt to restore an image file created from a larger drive onto a smaller drive this feature is beneficial assuming the image file does not exceed the capacity of the target drive. Restored partitions will occupy the same ratio of space as the model system. For example: The model system was a 1 GB drive occupied by two 500 MB partitions. The target computer has a 2 GB drive. The image will then occupy two 1GB partitions when imaging is complete.
Q Can I keep the partitions the same size as the model drive I created the image file from?
A Yes, if you choose that option from the Options drop down menu therefore disabling the automatic resizing mentioned in the above question.
|
ImageCast is a trademark, and the Micro House logo registered trademarks of Micro House International, Inc.
© 1997 Micro House International Inc. All rights reserved.
©1997 NetVersant Technologies. All rights reserved.
For further information, please call
(800) 274-6065 or e-mail NetVersant. |
| |
