Ran into this on my current engagement, here is the rundown:

source server windows 2008 (non R2) Destination Windows 2008 R2

Robocopy with the following commands:

robocopy \\”source server”\E$\”source path” \\”destination server”\d$\”destination path” /e /mir /XD “$RECYCLE.BIN” “System Volume Information” “pagefile.sys” /sec /MON:1 /np  /mt /tee /log:c:\logs\backup_log.txt

I used the version of robocopy that was included with windows and ran this on the destination server.  I used the “;NET USE \\”source server”\IPC$ /USER:”  command to specify the credentials prior to beginning the robocopy command.

I ended up having to do the following to get decent performance, install the following hot-fix (which allows you to specify which types of attributes and data streams to ignore with new command line arguments)

Significantly slower directory tree replication performance when you use the Robocopy command in Windows 7 or in Windows Server 2008 R2

http://support.microsoft.com/kb/2646535

I added the following command line switch to limit the number of retries in case a few files were locked (like system or app files which may have help up the replication due to the default setting being 1 million retries)

/r:10

after the hotfix i added this switch to improve the performance:

/NODCOPY

in addition i also broke up the job into multiple scripts which ran concurrently to improve efficiency.

I will post a few screen captures at the end. i will use Beyond Compare to analyze and publish the results.  We are cutting over a large file share from a colo environment to a managed services environment and i chose robocopy since that is the tool i always use. 9TB of data is copying as i write this. At the current rate it looks like it will take a week. prior to the hotfix and retries switches it looked like it may have finished in 2014. I wish i was joking.

I am still getting a few of these errors now and then:

Error 64 The specified network name is no longer available… which is driving me batty, it may be a bad filter driver from an old backup software or AV software or something else. At this point i am inclined to let it complete and then investigate.

I ran across this article this morning, read it here, or follow the link to slashdot

http://slashdot.org/topic/datacenter/wozniaks-predictions-for-2013-the-data-center-mobility-and-beyond/

Apple co-founder Steve Wozniak predicts great things for data centers in 2013, along with an interesting take on BYOD.

Ran across this today:

http://support.citrix.com/article/CTX116357

Summary

This article describes how to configure Web Interface to launch certain applications in Windowed mode.

Background

You might run into problematic applications that do not work properly when launched seamlessly. You might want to disable seamless for these applications but launch the rest of the applications seamlessly.

This can be done but the solution differs depending on the version of Web Interface in use.

Procedure

The following are examples of a published Notepad. Ensure that you use the name of the published application exactly as it is shown in the application set of the Presentation Server Console.

Note: Most of the settings in ICA files are not case sensitive, although the DesiredHRES and DesiredVRES settings in this article are case sensitive.

For Web Interface 5.x

For Web Interface 4.5 or 4.6

For Web Interface 4.0

For Web Interface 3.0

For Web Interface 2.0 (XP)

More Information

You can set DeisredHRES and DesiredVRES to any desired resolution, such as 800×600 or 1024×768.

If you want to run the application in a percent of screen size, then after TWIMode=Off, add the line ScreenPercent=90 which sets the screen to 90 percent.

This can also be done with the Program Neighborhood Agent site, just ensure that you edit the corresponding file under the conf folder for that site (Inetpub\wwwroot\Citrix\PNAgent\conf).

If you are using the 10.x client, and editing the default.ica or template.ica file, then only add the TWIMode=Off line. It obtains the HRES and VRES settings from the published application properties. Otherwise, you can receive an error about duplicate entries in the ICA file when a user tries to launch the application.

Recently i ran across an issue installing .Net Framework patches from Microsoft,, these new updates (KB2633870 & KB2600217) failed with code 800B010B.

It looks like a GPO we have in place may have changed a default setting that addresses how CERT Revocation is handled. I tried a few things in resolving the issue, thinking the issue was related to out of date root certs on the PC, i ran the following commands

certutil -URLCache -f http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl
certutil -URLCache -f http://crl.microsoft.com/pki/crl/products/MicCodSigPCA_08-31-2010.crl

Read the following for information on Root Certificates : http://support.microsoft.com/kb/931125.

That didn’t seem to fix the issue, ultimately, i found the answer on a German Blog ( http://bent-blog.de/fehler-80070643-und-800b010b-bei-microsoft-net-4-windows-updates-kb2656351-kb2656368-und-kb2600217/)

The key is to change the Software Publishing State Key Value within the registry:

[HKCU\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing]

Change the DWORD Key “State” with value 0xc9 to the value 0×22849

After changing the value, i was able to install the update without incident.

I am hoping this post saves my readers the trouble of finding the fix.