Citrix: Internet Explorer Intranet Zones

It appears that Citrix and Terminal Services does not allow Internet Explorer Security Zones to be modified from inside a Citrix Session. We used to have a Group Policy that set our Zone settings, but for some reason did not apply to our Citrix or RDP sessions.

There was a fix I found on the net that uses a Group Policy Object to resolve this.

The setting is in Administrative Templates | Windows Components | Internet Explorer | Internet Control Panel | Security Page | Site to Zone Assignment List

Enable that policy and fill it with the sites you need.

1 = Intranet Zone
2 = Trusted Zone
3 = Internet Zone
4 = Restricted Zone

eg. http://soeteam.blogspot.com Value 1.
Means http://soeteam.blogspot.com will be added the the Intranet Zone. You will be able to see this within IE.

After I applied this Group Policy I needed to log onto the console of the Citrix servers and run 'gupdate /force'

Source: http://www.trevorprokop.com/?p=11

Telstra Ultimate USB modem using Ciscos VPN Win 7

Install Latest firmware then install drivers.

http://www.sierrawireless.com/en/sitecore/content/Sierra%20Wireless/Support/Downloads/AirCard/USB_Modems/Telstra_Ultimate_AC312U.aspx

Disable “Windows 7 Mobile Broadband” in the telstra Watcher "user options"

Ref

http://forums.whirlpool.net.au/archive/1709121

Lync 2010: Migrate OCS 2007 R2 user to Lync 2010

The below process shows how to migrate an OCS 2007 R2 user to Lync 2010. This cannot be done using any GUI driven tools (at time of writing)

Note: Lync users cannot use the Microsoft Office Communicator 2007 client to log into Lync 2010. If the user to be migrated is logged in and using the Communicator client they will be automatically logged out and an error message informing the user to upgrade their client.

1. Launch the Lync Server Management Shell from your Lync Server

2. Type command: Move-CsLegacyUser -Identity username -Target lyncserver.yourdomain

3. Confirm the user move.

4. You're done.

Install the Lync 2010 client and enjoy. :)

ERROR: A temporary profile is loaded after you log on to a Windows 7-based system

To resolve this problem, follow these steps:
1. Log on to the system by using an administrative user account other than the user account that is experiencing the problem.
2. Back up all data in the current user's profile folder if the profile folder still exists, and then delete the profile folder. By default, the profile resides in the following location:%SystemDrive%\Users\UserName
3. Click Start, type regedit in the Start Search box, and then press ENTER.

If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
4. Locate the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
5. Under the ProfileList subkey, delete the subkey that is named SID.bak. 

Note SID is a placeholder for the security identifier (SID) of the user account that is experiencing the problem. The SID.bak subkey should contain a ProfileImagePath registry entry that points to the original profile folder of the user account that is experiencing the problem.
6. Exit Registry Editor.
7. Log off the system.
8. Log on to the system again.
After you log on to the system, the profile folder is re-created.

Source:
http://support.microsoft.com/kb/947242/en-au

ERROR: Microsoft Lync 2010 must be installed by running the appropriate Lync setup executable

Issue:

You experience the following symptoms:

• A local Windows Installer (MSI) installation for Microsoft Lync 2010 can fail, and the following warning is displayed in the Microsoft Lync 2010 Setup dialog box:Microsoft Lync 2010 must be installed by running the appropriate Lync setup executable


Resolution:

Use the Lync 2010 UseMSIForLyncInstallation Group Policy setting to enable or block MSI deployments for Lync.msi as follows:

Name: UseMSIForLyncInstallation

Default: 0

Range: 1 or 0

Registry Location:HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator

To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following registry subkey HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Communicator

3. On the Edit menu, point to New, and then click DWORD Value.

4. Type UseMSIForLyncInstallation, and then press ENTER to name the registry entry.

5. Right-click UseMSIForLyncInstallation, and then click Modify.

6. In the Value data box, type 1 if that value is not already displayed, and then click OK.

7. Exit Registry Editor.

8. Restart the Windows client.

Source:

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

Error 53: When trying to map to server using net use

Scenario:

You receive "status 53" when running net view or net use to attach or map to a Windows server.

eg. You type the command:

C:\>net view \\server

Results

Shared resources on \\server

Share Name Type Used as Comment

------------------------------------------------------------------------------------------------

Command failed: status 53

C:\>

Resolution

Your Windows Server you are trying to connect to does not have any WINS addresses entries listed in Advanced TCP/IP Settings. Add at least one entry and apply settings.

TIP: Office 2010 Volume Activation Tips and Tricks

Ospp.vbs

This handy script is helpful for performing local and remote licensing operations for Microsoft Office 2010. You can find it in the “%ProgramFiles%\Microsoft Office\Office14” folder. For 32-bit installs of Office on 64-bit operating systems, look for it under the “Program Files (x86)” folder. Keep in mind ospp.vbs is the script to configure the Office 2010 client, while slmgr.vbs is used to configure the KMS host and Windows installations.

To run this script, open an elevated command prompt by clicking the Start button and searching for “cmd” in the search box. Right click on the command prompt window and select “Run as administrator.” Go to the directory with this command:

cd “%ProgramFiles%\Microsoft Office\Office14”

You can see the options that are available by typing:

cscript ospp.vbs -?

Richard Moloney, the developer of this script, says a useful benefit after setting up a KMS host is using the -act and -dhistory commands to verify the Office client is finding the KMS host and successfully activating. He suggests, “If you’re setting up a KMS host, you can manually trigger and verify successful activation. You don’t need to wait 25 days until notification dialogs start popping up to start troubleshooting.”

Trigger activation and view the KMS activation history by running:

cscript ospp.vbs –act

cscript ospp.vbs –dhistory

For MAK activation, one common task would be to check the status of your computer, install a Professional Plus Beta MAK key, and trigger activation. Run these commands (if you’re pasting these commands, you may need to change the long dash to a short dash). In this example, note that when you run the –act command, you’ll be triggering MAK activation, which goes to Microsoft’s activation servers, not your KMS host.

cscript ospp.vbs –dstatus

cscript ospp.vbs –inpkey:22HGX-728MX-BBWX9-7BB8X-J96B4

cscript ospp.vbs –act

cscript ospp.vbs –dstatus

What if you got an error code? You can easily get the error description with this command specifying the error code:

cscript ospp.vbs –ddescr:0xC0020017

You can even run this script to check the status or trigger activation of a remote computer. Just provide the computer name and login credentials:

cscript ospp.vbs –act

Source: http://blogs.technet.com/b/office2010/archive/2009/12/18/volume-activation-tips-and-tricks.aspx