Check it out here! http://boisecomputing.com/free-software-giveaway-winx-dvd-copy-pro First come first serve.

Check it out here! http://boisecomputing.com/free-software-giveaway-winx-dvd-ripper First come first serve.

** UPDATE ** All 6 License keys have now been given away.

I have 6 free licensed copies of WinX Blu-ray (valued @ $39.95!) to give away that I received from Digiarty Software. The first 6 people to comment on this post will get the licenses, one per person.
Make sure to include your email address in the comment form.

WinX Blu-ray Decrypter (DESCRIPTION)

WinX Blu-ray Decrypter is a professional Blu-ray decrypting and copy tool for users to decrypt and backup Blu-ray to M2TS video file or Blu-ray folder (compatible with Win7 Media Player). It is able to remove and decrypt encryption (AACS MKB v25), BD+ copy protection, etc. in Blu-ray disc. With this program, you can effortlessly protect your beloved Blu-ray discs from scratch or loss.

WinX Blu-ray Decrypter is an ideal Blu-ray backup solution which supports both Full Disc Blu-ray Backup and Title Copy modes. It allows you to decrypt Blu-ray Disc with all known copy protections and encryptions and backup 3D Blu-ray to 2D video in only 3 clicks. It also brings fast decrypting speed while preserving original video/audio quality. If you are looking for powerful software to backup and decrypt Blu-ray video disc, WinX Blu-ray Decrypter is the way to go.

Product URL : http://www.winxdvd.com/blu-ray-decrypter/

PS: These license codes are valid before Nov.15, 2011. Please register it before expiration date.

Enjoy!

SPREAD THE WORD, TOGETHER WE HAVE CONQUERED SYSPREP

This is version 2 of a step by step guide on Sysprepping a Windows 7 machine from start to finish. I cannot take full credit on this because my first article had so many helpful comments and discussions that this is simply a combination of all the good advice written into a working guide. (I would especially like to thank George for his input on Cscript for auto activation and Nathan for input on Sysprep Audit Mode). This will guide you through the following:

- Audit Mode
- Building the unattend.xml file in WSIM
- copyprofile=true command to copy the default profile (no manual copy)
- Prompt for a computer name
- Enable Administrator account
- Administrator account logs in first time automatically
- Activate windows automatically with Cscript;
- Successfully copy over taskbar icons;
- Delete unattend.xml file automatically upon completion of re-image.

Here is a list of what you will need:

- Latest version of WAIK : KB3AIK_EN.iso Version 1.0
- Windows Vista or Windows 7 Machine to build the XML file on
- ISO or DVD of Windows 7 Installation (x32 or x64)
- WinPE Boot Environment : BrianLeeJackson WinPE 3.0 BootLoader

First we are going to walk through building the unattend.xml file (answer file) and then we will walk through the actual Windows 7 imaging process.

PART 1 – XML FILE CREATION

Step #1

If you have a Windows 7 installation DVD, insert it now. Or if you have an ISO of 7, go ahead and extract it to a folder on your desktop. (I recommend 7-zip).

Step #2

Launch Windows System Image Manager. Your start menu should look like the image below:

Windows 7 WAIK Version 1

Step #3

Under the “Windows Image” header, right click and select new image.

Windows System Image Manager

Step #4

You will now want to browse to the .CLG file in your Windows 7 installation (I am using Windows 7 Enterprise x64 in my example). It is located in the sources folder. See Image below. You can select either the .clg file or the install.wim. Both will have the same result.

Selecting CLG File - WSIM

Step #5

Now we need to create a new answer file. Go to the file menu and select “Create New Answer File.” Right after creating one, go ahead and simply go to file menu and select “Save Answer File.” This will give your XML file a name and save location. I chose to name mine unattend.xml. Now you see we have two category folders, Components and Packages. Under the Components folder you see that we have 7 options:

-1 windowsPE
-2 offlineServicing
-3 generalize
-4 specialize
-5 auditSystem
-6 auditUser
-7 oobeSystem

Step #6

These are very important as these are the steps in which the unattend.xml file is sequenced.
The next part is a little confusing. You are going to add components, from under the “Windows Image” section on the bottom left hand side to the passes on your Answer File. To add a component, you can right click on them and select “add to # pass”. There are many different options you can add, but they have to be done in a certain order and pass otherwise your sysprep might fail. I am simply going to use the one I created as the example.

Answer File - Unattend.xml

Here is more information about adding options under the passes:

1 windowsPE

Nothing required in my example.

2 offlineServicing

Nothing required in my example.

3 generalize

amd64_Microsoft-Windows-Security-SPP_6.1.7600.16385_neutral

Set 1 for SkipRearm to allow up to 8 rearms

4 specialize

amd64_Microsoft-Windows-Deployment_6.1.7600.16385_neutral

1. 1. Order: 1
      path: net user administrator /active:yes
      WillReboot: Never

   RunSynchronousCommand[Order="1"]

RunSynchronous

amd64_Microsoft-Windows-Security-SPP-UX_6.1.7600.16385_neutral

SkipAutoActivation: true

amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral

Computer Name: Leave blank (we will deal with this at the end)
CopyProfile: true
Registered Organization: Microsoft (you must leave this in this section)
Registered Owner: AutoBVT (you must leave this in this section)
ShowWindowsLive: false
TimeZone: Pacific Standard Time

(Please view TimeZone settings here -> http://technet.microsoft.com/en-us/library/cc749073%28WS.10%29.aspx)

You can delete other sub-header components if you don’t need them.

5 auditSystem

Nothing required in my example.

6 auditUser

Nothing required in my example.

7 oobeSystem

amd64_Microsoft-Windows-International-Core_6.1.7600.16385_neutral

InputLocale: en-us
SystemLocale: en-us
UILanguage: en-us
UserLocale: en-us

amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral

RegisteredOrganization: Your Company Name
RegisteredOwner: Your Name

AutoLogon

1. Password: Administrator Password

Enabled: true
LogonCount: 5
Username: administrator

FirstLogonCommands

1. CommandLine: cscript //b c:\\windows\\system32\\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (windows 7 license key)
   Order 1
   RequiresUserInput: false
   CommandLine: cscript //b c:\\windows\\system32\\slmgr.vbs /ato
   Order 2
   RequiresUserInput: false

SynchronousCommand[Order="1"]

SynchronousCommand[Order="2"]

OOBE

HideEULAPage: true
NetworkLocation: Home
ProtectYourPC: 1

UserAccounts

1. 1. 1. Password: Administrator Password

      Action: AddListItem
      Description: Local Administrator
      DisplayName: Administrator
      Group: Administrators
      Name: Administrator

   LocalAccount[Name="Administrator"]

AdministratorPassword: Administrator Password
LocalAccounts

If you have questions, look at my image above to see full layout of components, it should help.

Step #7

K, now go ahead and save your answer file as unattend.xml.

Step #8

If you want the sysprep to prompt for a computer name you need to remove a line from your XML file. Open up your XML file you saved with notepad and remove the following line:

Unattend.xml Computer Name

PART 2 – IMAGING PROCESS / RUNNING SYSPREP

Step #9

Install Windows 7 (Enterprise) from CD or USB flash drive, when you arrive at the welcome screen and it asks you to create a username, hit ctrl+shift+f3.
This will reboot your machine and put your windows build in ‘audit’ mode.

Step #10

On reboot, you’ll automatically be logged in under the built-in Administrator account. A sysprep GUI box will appear, but you can close it and NOW begin to customize your profile.

Step #11

Install any software/drivers, make any profile customizations, etc.
If you need to reboot, the computer will boot you back into the Administrator account. You will be stuck in this audit mode until you run sysprep with the /oobe parameter. After doing so, sysprep will delete/clean up the Administrator account, but if you have copyprofile=true in your unattended answer file, it will copy the customized Admin account to the default profile before deleting it.

Step #12

On the PC you are going to be running sysprep on, you need to create a folder called scripts in this directory: %WINDIR%\Setup\. Now you are going to create a CMD file within the %WINDIR%\\Setup\\Scripts directory. Right click and make a new text file called SetupComplete.txt. Remove the .txt extension and replace that with .cmd. You now have a SetupComplete.cmd file which windows will read the first time it boots up from the sysprep. We need to place a script inside the CMD file. Edit the cmd file with notepad and insert this line: del /Q /F c:\\windows\\system32\\sysprep\\unattend.xml. This script will delete your unattend.xml file after it has been used. The unattend.xml file is also copied to the C:\\Windows\\Panther directory, so you will want to add a second line to the CMD file, del /Q /F c:\\windows\\panther\\unattend.xml. If you have passwords or cd keys stored in that xml file you don’t have to worry about it being left on the computer.

UPDATE AS OF JUNE 16TH: Read my Taskbar Icons Tutorial before continuing.

Step #13

Once you have everything configured correctly, Copy or move your unattend.xml file to : C:\windows\system32\sysprep. Now to run sysprep, navigate to that sysprep folder, hold SHIFT and right click and select “Open New Command Windows Here”. Next, input the following commands:

sysprep /generalize /oobe /shutdown /unattend:unattend.xml

Step #14

Turn the computer back on and boot to WinPE 3.0 environment (USB stick or CD/DVD). You can use my BrianLeeJackson WinPE3.0 BootLoader to boot up from USB or CD and capture your image. Capture image and save image to network location.
A Dell 960 or GX755 is a good standard for capturing when you want a generic image for use with multiple systems. Might require injecting additional drivers for 3rd party brands, HP, etc. Most should work though right out of the box.

Step #15

On reboot, Windows will run out of the box, as the /oobe is intended. As long as you put your cd key into the unattend.xml file, windows will be activated automatically in the background, you will be automatically logged into the administrator account, and the unattend.xml file is deleted. You are now ready to use the computer or join it to the domain. Enjoy!

Anti-Virus Applications with Known Issues

• Norton 2009
• McAfee
• AVG
• Avira
• ESET NOD32 4.0 (User reported issues)

Anti-Virus Applications 100% Compatible with Sysprep

• Microsoft Forefront
• Microsoft Security Essentials

And yes, you probably noticed that both applications are made by Microsoft, go figure. If anyone notices any other anti-virus programs that are causing issues with sysprep please comment on here. Or if you have workaround for these anti-virus apps and sysprep working together please comment.

Microsoft Security Essentials - Free Alternative

CHANGES/UPDATES AS OF NOVEMBER 12, 2009

• Added new Windows 7 winpe.bmp wallpaper for WinPE 3.0 Boot Environment, both x32 and x64.
• Added new drivers for WinPE 3.0 environment including some netbooks and HP eCopy machines, x32.
• Added the newest stable version of GimageX v2.0.17, x32 and x64.
• Removed GHOST from packages, x32 and x64.

Also, if you have enjoyed my site or gotten useful information from it; even if I saved you an hour from compiling different information then I have accomplished my goal. However, I am now getting 10-20 emails per day asking questions about sysprepping, Windows 7 deployment, etc. It is getting hard to keep up. And with this increase in traffic comes an increase in bandwidth. If I have helped you in any way please feel free to donate any amount on the right hand side so I can keep this blog going. I have some great new tutorials planned as I jump deep into the Acresso’s AdminStudio 9.5 Repackager for Windows 7 x64.

Step #1

Unplug your Zune from USB and close your Zune software.

Step #2

Go to your control panel.

Zune Control Panel

Step #3

Click on Clock, Language, and Region

Zune Region Settings

Step #4

Click on “change location”.

Zune Change Location

Step #5

Change your location to “United Kingdom”.

Zune UK

Step #6

Now plug your Zune back in and launch the Zune software. Go to settings at top right and then to “Player Update” on left hand side.

Zune Player Update

Step #7

It should now ask you to upgrade player to 4.3. Select “Upgrade”. This will take a minute or two.

Step #8

You should now see a confirmation screen saying your player is fully up to date.

Zune Player 4.3

Step #9

You can now go back to control panel and change your region back to US.

If you are like me you have probably run into the following error when trying to run powershell scripts. This becomes very annoying and tedious if you are running different scripts on a regular basis.

“Security Warning – Run only scripts that you trust. While scripts from the Internet can be useful, this script can potentially harm your computer. Do you want to run –.ps1? [D] Do not run [R] Run once [S] Suspend [?] Help (default is “D”):

Step #1

The first thing you need to do is launch Windows Powershell.

Step #2

Then enter the following commands:

get-executionpolicy

set-executionpolicy bypass

Powershell Trust Scripts

Now launch your script and enjoy not seeing that annoying message come up.

If you are on the same network, or Vlan, or subnet as someone else you will probably notice that if you ping their hostname it will return with a IPv6 address.

If you want to still see what their IPv4 address is then simply use the command below:

ping hostname -4

Simply add a “-4″ after your normal ping command.

Rudi De Vos over in the UltraVNC forums posted a fix for this problem.

Also, here is the link for the newest version of UVNC.

I have tested Rudi’s fix in test environment and we are now using this in production environment within Windows 7 environment and it is working great. Thanks Rudi!

UVNC Listener