Windows Registry Editor Version 5.00
AntiVirus and firewall may also be something else to consider.
|The Iron Hedge||
One possible solution to this is to do the following:
Windows Registry Editor Version 5.00
AntiVirus and firewall may also be something else to consider.
AIK Version 1: startnet would load ghost right away, however, IP was slow to be detected and could not connect to a session
AIK Version 2 (aka for Windows 7): would wait for IP address before launch application.
PROBLEM: When I start a Multicast, I loose network connection or limited traffic.
SOLUTION: To throttle your multicast bandwidth usage:
From the WDS MMC, open the Server Properties page. Go to the Network Settings Tab. Select the Custom network profile.
In the registry, browse to HKLM\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSMC\Profiles\Custom and set the TpMaxBandwidth setting to something less than 100. It's the percentage of available bandwidth that the server uses.
Setup GHOST32.exe inside a WIM image (Legacy Mode not supported in 2008)
1. Download the Windows Automated Installation Kit (WAIK) located at the following URL:
2. Once you have WAIK download, burn the image file to DVD using 3rd party burning software or extract the contents of the image file to a folder.
3. The following components should be installed on a Windows XPSP2, Windows 2003 SP1, or Windows Vista computer. These components are all available on the WAIK DVD burned in step 2.
a. .NET Framework Setup
b. MSXML 6.0 Setup
c. Windows AIK Setup (install last).
4. Click Start > All Programs > Microsoft Windows AIK > Windows PE Tools Command Prompt
5. Type the following commands at the command prompt:
a. copype.cmd x86 c:\winpe_x86
b. imagex /mountrw c:\winpe_x86\winpe.wim 1 c:\winpe_x86\mount
Next, you'll want to copy ghost32.exe, NIC drivers, and Mass Storage Controller Drivers to the PE disk. The NIC drivers and Mass Storage Controller drivers need to be Vista drivers.
c . copy "C:\Program Files\Symantec\Ghost\Ghost32.exe" c:\winpe_x86\mount\windows
d. copy "[NIC driver location]" c:\winpe_x86\mount\windows (Vista Drivers only)
e. copy "[Mass Storage Driver Location]" c:\winpe_x86\mount\windows (Vista Drivers only)
f. peimg /prep c:\winpe_x86\mount\windows
Type Yes to continue
g. imagex /unmount c:\winpe_x86\mount /commit
h. copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim
Type Yes to overwrite
i. oscdimg -n -bc:\winpe_x86\etfsboot.com c:\winpe_x86\ISO c:\winpe_x86\winpe_x86.iso
j. Burn the ISO located at c:\winpe_x86 to CD/DVD.
6. Boot your client machine with the new PE disk you built
7. When the PE environment is fully loaded, you'll see a command prompt. At the command prompt, type ghost32.exe and press [enter]
8. At this point, Ghost will open and you can perform imaging as you normally would:
a. Click GhostCast
b. Select Unicast/Multicast/Directed Broadcast
c. Type the name of the GhostCast Session to join
d. Click OK
e. Select the source/destination drive and Click OK
f. If you're creating an image, choose the level of compression to use. If you're restoring an image, you won't see compression options.
g. Click Yes when asked, "Proceed with Image File Creation?"
Note: To automate the opening of Ghost32.exe when you boot into the Windows PE environment, modify the startnet.cmd file prior to taking step 5E. You can find the startnet.bat file in c:\winpe_x86\mount\windows\system32\startnet.cmd. Underneath the winpeinit entry, enter the following command line and resave the file:
How to...Windows Vista PE, WDS and Ghost 8!
I have been playing around with the new Deployment options with Windows Vista.
I have achieved a working setup that now uses Windows Deployment Services and Windows PE to deploy our Ghost images.
Our Deployment Setup (What this procedure helps acheive)
To deploy our Ghost images on our student machines we use PXE capable machines.
The client machines boot up we choose F12 to initiate Network Boot.
At this stage the client machine receives a DHCP address and then contacts a RIS/WDS server to receive a boot menu.
The RIS/WDS server displays a menu on the PXE client machine and then we can choose from a number of *.wim images configured on the RIS/WDS server.
*.wim images are a new Microsoft Image format allowing more flexibility in the area of OS deployment.
The procedure below specifies how to create a customised Windows PE *.wim file to be used in this deployment strategy.
If you are interested in the setup then read onwards�.
1. The WinPE/Ghost32 image works on most machines simultaneously. Thus we can use one client image for all machine types.
2. WDS allows for quick and easy installs of Windows Vista etc.
3. No need for RIS 3rd party software like RISME
1. Speed? The WinPE/Ghost32 images take longer to boot up than the old DOS/Ghost images.
2. New skill needed to create/customise the WinPE images
What do you need?
The Business Desktop Deployment Tools for Vista 2007.
I downloaded them as part of my connect.microsoft.com subscription (The New Microsoft Beta site).
The parts of the BBD 2007 you need are:
o Windows Automated Installation Kit (Windows AIK)
o Windows PE
o WDS update
Install the BBD 2007 on an administrative PC
The WDS update will be installed as part of this under c:\program files\BDD 2007\WAIK\WDS\
Install WDS (Windows Deployment Services) on the image server
Firstly to enable us to use the new Microsoft *.wim format of their CD images I had to deploy WDS (Windows Deployment Services) on our image server.
WDS has the ability to work in conjunction with Microsoft RIS, so while I was tweaking things to work with Windows PE images we are still able to use the old legacy RIS images (using the RISME product) to deploy our course Ghost images.
Install the Windows AIK on the administrative PC
This will be found under c:\program files\BDD 2007\WAIK\
You will install the WAIK to c:\program files\Windows AIK\
Use the Windows AIK to create a customised Windows PE image
You will need to do this for every *.wim image you wish to create. I have used the example below when I created the Windows PE client image to start a Ghost32 client Mulitcast session called auto1.
1. Open a command prompt as administrator
2. C:\program files\windows AIK\tools\PETools\
3. copyPE x86 winpeghost32-auto1
***this creates a WinPE working directory called �winpeghost32-auto1�***
4. imagex /mountrw winpe.wim 1 mount
***this mounts the *.wim file as a sub-directory called �mount�***
5. cd mount
6. cd windows
7. md ghost8
8. copy ghost32.exe into the ghost8 directory
***you can use Windows Explorer to do this***
9. go to the \mount\windows\system32\ directory
10. edit the startnet.cmd file
***you can use Notepad to edit as follows***
%systemroot%\ghost8\ghost32.exe -clone,mode=restore,src=@mcauto1,dst=1 -sure -rb -fdsp
***this will tell WinPE how to start up***
***wpeinit starts the PE networking components and PnP***
***wpeutil disablefirewall this must be done for multicast to work***
*** %systemroot%\ghost8\ghost32.exe -clone,mode=restore,src=@mcauto1,dst=1 -sure -rb fdsp will start ghost client***
***wpeinit reboot will reboot the client once the Ghost client is finished downloading***
12. cd mount
13. peimg /prep windows
***this will shrink the size of the image***
16. imagex /unmount /commit mount
***this will unmount the image as save your changes***
17. You will now have a customised WinPE.wim file in the /winpeghost32-auto1/ directory.
18. I have been then renaming the WinPE.wim file to something like winpeghost32-auto1.wim to avoid confusion.
Deploy the winpeghost32-auto1.wim to the WDS server
Do this by opening up WDS in administrative tools
Add the winpeghost32-auto1.wim boot image to the boot images folder by using right click.
Test out the WDS client
When you boot up you client PCs now you will still need to choose F12 to initiate the Network Boot. When you do this a new WDS menu will appear with the deployed *wim images listed.
If you wish to still use you old RIS based images then choose Remote Installation Services which should be the bottom menu option.
I hope this helps
How to add drivers into your WIM image:
Installing the LAN driver
peimg /inf=C:\winpe_x86\<Driver Location>\<Driver.inf> C:\winpe_x86\mount\Windows
When you try to remove a domain controller from your Active Directory domain by using Dcpromo.exe and fail, or when you began to promote a member server to be a Domain Controller and failed (the reasons for your failure are not important for the scope of this article), you will be left with remains of the DCs object in the Active Directory. As part of a successful demotion process, the Dcpromo wizard removes the configuration data for the domain controller from Active Directory, but as noted above, a failed Dcpromo attempt might leave these objects in place.
The effects of leaving such remains inside the Active Directory may vary, but one thing is sure: Whenever you'll try to re-install the server with the same computername and try to promote it to become a Domain Controller, you will fail because the Dcpromo process will still find the old object and therefore will refuse to re-create the objects for the new-old server.
In the event that the NTDS Settings object is not removed correctly you can use the Ntdsutil.exe utility to manually remove the NTDS Settings object.
If you give the new domain controller the same name as the failed computer, then you need perform only the first procedure to clean up metadata, which removes the NTDS Settings object of the failed domain controller. If you will give the new domain controller a different name, then you need to perform all three procedures: clean up metadata, remove the failed server object from the site, and remove the computer object from the domain controllers container.
You will need the following tool: Ntdsutil.exe, Active Directory Sites and Services, Active Directory Users and Computers.
Also, make sure that you use an account that is a member of the Enterprise Admins universal group.
Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.
To clean up metadata
Note: Windows Server 2003 Service Pack 1 eliminates the need for the above step.
metadata cleanup: Remove selected server "CN=SERVER200,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=dpetri,DC=net" removed from server "server100" metadata cleanup:
At this point, Active Directory confirms that the domain controller was removed successfully. If you receive an error that the object could not be found, Active Directory might have already removed from the domain controller.
To remove the failed server object from the domain controllers container
To remove the failed server object from DNS
Also, consider the following:
I had a computer that was running an executable causing the computer to use resources to the max. Eventually I found out it was apart of Adobe Reader version 9 on Windows 7. Uninstalling Adobe, resetting the computer and installing the latest Adobe Reader will fix this problem.
Unfortunalty at the time of writting the was no such software that was able to do this all-in-one. However, a solution was still at hand thanks to software around on the internet. Ill be writting this up to hopefully assist others with this enquiry. This is only a rough guide and does not go into detail on how to use the applications but they are very easy to use.
First we need to convert the video to a Computer friendly format. Software I used to do this was Handbrake, Dr. Divx or AVS4YOU. Once converted you will need software that can turn the video frames into jpeg. The software I used for tis was from DVDsoft http://www.dvdvideosoft.com/ Free Video to JPG Converter 1.8. Another alternative is SC Free Video Decompiler unfortunalty I dont have a program for other platforms to do this other than windows but if anyone knows of software (free if possible) for any other platforms comments would be great.
Once the frames have been exported I used a tool called "Google Picasa". This is a brilliant tool however, on startup it wants to scan your whole computer or just documents (version 3.6), it will not give you an option on just one folder however, there is a solution. Start Picasa and select what ever option you want, then under "Tools" go to "Folder Manager" from here you can tell is to "remove from picasa". This way face detection will only work in the folder you allowed. Once the faces have been found you can then select the faces you want and export them. All done.
Im a Network Administrator for a school. I have a strong interest in education and how education is taught. I teach students about the insides of computers on the rare occasion and teach many teachers about computers and how ICT can be used giving advantage to students learning. I'm also interested in Music, History, Ancestry, Science, Electronics etc. Hope you enjoy my blogging.