Windows7 Folder Redirection - Does it work with Windows server 2008 SP1?

http://www.youtube.com/watch?v=eExoyGQjvX8

I have run across this same problem today.  I am testing Win7 in my student labs and need to direct Documents to their networked H: drive as I do not allow them to have profiles, so when they logout, anything that they would have saved to 'Documents' would go *poof*.  It was very simple on XP, when I try to redirect with W7, the H: doesn't even show up, when I select it manually it says I can't use it because it's not able to be indexed?? 

There is a group policy for that. You will need the Windows 7 GP's loaded though on a Windows 7 or Windows 2008 R2 server to see them.

The policy is User Configuration - Admin Templates - Windows Components - Windows Explorer - Turn off Windows Libraries features that rely on indexed file data = Enabled.

Also make sure you do Folder Redirection and tick the box "Also apply redirection policy to windows 2000 etc" in the Settings of the Folder Redirection. (only seen on Windows 7 or Windows 2008 R2). If Folder redirection is created on Windows 2003 it is auto ticked.

Server 2008 - Printer Setup Using Group Policy

System available:

1. Server - Windows Server 2008 - 64 bit
2. Client - Windows XP / Windows 7 - 32 bit

Requirements:

1. To deploy printer connections by using Group Policy, your environment must have the Active Directory Domain Services (AD DS) schema
2. Driver - You need both 32 bit and 64 bit driver in this case. You can add additional driver using Print Management. Now a days there is Universal Driver available for Lexmark & HP printers. Printers driver 32 bit & 64 bit both of them has to be exactly same name and version.
3. You need PushPrinterConnection.exe 32 bit version because it will run on the client side. So Run this into every pc joined in AD using GroupPolicy Management->Compuer Configuration->Policies->Windows Settings->Scripts(Startup/Shutdown)
4. Print Management to Install Drivers and Printers & Deploy it via GroupPolicy

Client Side:

1. PC is already joined to AD
2. PC will run PushPrinterConnection.exe during startup. You can do it by GroupPolicy.

Cannot create HTTP web project IIS Installation - Windows7 - ASP.NET

To use the IIS feature you need to install - IIS Metabase and IIS6 configuration compatibility.

Cannot ping - Windows7

I am going through this to get shared folders on the Windows 7 computer visible on other computers on the network. Obviously this is not working. Just to recap the configuration:
1) all computers on the network are members of same Workgroup
2) My documents on the Windows 7 computer are shared read-write with everyone
3) advance sharing options show:
Network discovery ON
File and print sharing ON - Turning this on solved my problem
Public folder sharing ON
128 bit encryption
Password protected sharing OFF
IPv6 disabled
Homegroup stuff either OFF or ON and managed by Windows (but this is irrelevant)
4) firewall off

Cannot Install Antivirus - Error message- Computer could not be contacted - Windows7

1. Disable Simple File Sharing (if the client computer is Windows XP).
2. Re-run the protect computers wizard, ensuring that you use a domain administrator account, as described in the 'Protect Computers' section of the Startup Guide.
3. If protection still fails, go to Windows services and ensure that the following services are running: (It solved my problem)
   • Computer Browser
   • Remote Registry
   • Server
   • Task Scheduler
   • Workstation
   • Windows Installer
4. Re-run the protect computers wizard.
5. If protection continues to fail, do the following:
   • To check that access is not being blocked by a firewall (either hardware or software), ensure you are able to browse to the client's C$ share:
     • Go to Start|Run and type in \\<clientname>\c$ (where <clientname> is the name of the computer experiencing the problem)
     • Press Enter.
   • Ensure that 'File and Printer Sharing for Microsoft Networks' is enabled in the 'Local Area Connection properties' for the adapter that the computer is using to connect to the network:
     • From Windows Control Panel, go to 'Network and Dial-up connections'.
     • Right-click the 'Local Area Connections' icon, select 'Properties', click the 'General' tab.
     • In the box that lists components/items used for the connection, ensure that 'File and Printer Sharing for Microsoft Networks' is selected.

How to Install Office 2010 KMS Host & Client

Important things to remember:

In order to activate MS Office 2010 unlike Windows7 KMS client you do not need MS Office 2010 KMS Client Key. You just need only one KMS host key to install it on Office-KMS-host-workstation. In client PC KMS client is pre installed so all you need to do is rearm Office 2010.

Requirements:

1. Windows Server 2008 R2 or Windows7
2. MS Office 2010 KMS Key
3. Allow TCT port:1688 and Key Management Service in Windows Firewall
4. 5 PCs - MS Office 2010 rearm manually and restart
5. Run command prompt as administrator
6. Run slmgr.vbs  command from C:\windows\system32\ directory otherwise it does not work
7. Open a browser in the KMS host server and check if you can go to internet

Set up a MS Office KMS host on Windows7 or Windows Server R2:

1. Download and run the KeyManagementServiceHost.exe file on Microsoft Office 2010 KMS Host License Pack(http://go.microsoft.com/fwlink/?LinkID=169244). on a supported operating system.
2. Enter your Office 2010 KMS host key when prompted.
3. Click OK to continue with activation.
4. 5 PCs - MS Office 2010 rearm manually and restart
5. Open port 1688 and allow the KMS host service through the firewall.

• Open Control Panel and click on the Windows Firewall icon.
• Click on the “Allow a program through Windows Firewall” link.
• Click on the Change Settings button.
• Check the box for Key Management Service.

Setup KMS Office Host Manually:

1. Open command promt with run as administrator
2. type command: c:\windows\system32\cscript slmgr /ipk KMS_Office_Host key 
3. type command: c:\windows\system32\cscript slmgr /dlv and look for "activation id" and make a note of "activation id" which you need in next step
4. c:\windows\system32\cscript slmgr /ato ACTIVATION_ID
5. Open port 1688 and allow the KMS host service through the firewall.
• Open Control Panel and click on the Windows Firewall icon.
• Click on the “Allow a program through Windows Firewall” link.
• Click on the Change Settings button.
• Check the box for Key Management Service.
6. 5 PCs - MS Office 2010 rearm manually and restart
7. To prevent instability in the license service, the system should be restarted or the Software Protection Service should be restarted. The following command lines can be used to restart the Software Protection Service: net stop sppsvc
    net start sppsvc

To determine whether a machine has the Office 2010 KMS Host License Pack installed and is an active Office KMS host, run a command line similar to the following:

• slmgr /dlv   and make a note of activation id
• cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864 
• The output of a machine which has the Office 2010 KMS Host License Pack installed will resemble the following. Key items are "Partial Product Key: GB7AH" and "License Status: Licensed", which indicate that the Office 2010 KMS host key is successfully installed and activated.

  Name: Microsoft Office 2010, KMSHost edition Description: Microsoft Office 2010 KMS, VOLUME_KMS channel Activation ID: bfe7a195-4f8f-4f0b-a622-cf13c7d16864 Application ID: 59a52881-a989-479d-af46-f275c6370663 Extended PID: 55041-00096-199-000004-03-1033-7600.0000-3632009 Installation ID: 008523674214771124199799184000850026888810090415321136 Processor Certificate URL: http://go.microsoft.com/fwlink/p/?LinkID=88342 Machine Certificate URL: http://go.microsoft.com/fwlink/p/?LinkID=88343 Use License URL: http://go.microsoft.com/fwlink/p/?LinkID=88345 Product Key Certificate URL: http://go.microsoft.com/fwlink/p/?LinkID=88344 Partial Product Key: GB7AH License Status: Licensed Remaining Windows rearm count: 1 Trusted time: 10/16/2011 2:07:42 PM Key Management Service is enabled on this computer     Current count: 0     Listening on Port: 1688     DNS publishing enabled     KMS priority: Normal

Configure Windows7 client for MS Office 2010 KMS activation:

1. Make sure all Office 2010 applications are closed.
2. Open an command prompt as Administrator.
   cd "C:\Program Files\Common Files\microsoft shared\OfficeSoftwareProtectionPlatform\"
   ospprearm.exe 
3. Go to %installdir%\%Program Files%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform. If you installed the 32-bit edition of Office 2010 on a 64-bit operating system, %Program Files% is the Program Files (x86) folder.
4. Run ospprearm.exe. If you see a message that states success, it has successfully rearmed your office application and you are ready for image capture.
5.  

Important:

Do not open an Office application, ospp.vbs, or anything related to Office 2010. Doing so starts the grace timer.

6. Capture the image or save the VM. For more information about how to capture the image, see Configure Office 2010 for a hard disk image.

Tools to configure client computers in Office 2010:

1. Run command promt as Administrator, type the following command and press enter:
   cscript "c:\Program Files\Microsoft office\Office14\ospp.vbs" /inpkey:MS_Office_Professional_Setup_Key
2. Type the following command and press enter to activate MS Office 2010 Professional:
   cscript "c:\Program Files\Microsoft office\Office14\ospp.vbs" /act
3. Type the following command and press enter to see the client status:
   cscript "c:\Program Files\Microsoft office\Office14\ospp.vbs" /dstatusall

How to check if Office client is rearming or not:

1. Go to Office KMS host machine or server
2. Open Event Viewer
3. Application and Services Logs
4. Key Management Services
5. Look for Event ID 12290 and open at least two computer events and in the general Tab match the following CMID key, if two of them are same then machine did not rearm successfully:
   An activation request has been processed.Info:0x0,5,MF6-7.scc.local,0c9cde55-66e9-4734-b561-628a79944f2a,2011/06/09 11:35,0,5,0,6f327760-8c5c-417c-9b61-836a98287e0c

Resources:

1. Deploy volume activation of Office 2010
   http://technet.microsoft.com/en-us/library/ee624357.aspx
2. KMS Activation Step:
   http://technet.microsoft.com/en-us/library/ff603508.aspx#section4
3. Volume Activation Technical Reference Guide:
   http://www.microsoft.com/downloads/en/details.aspx?FamilyID=857c6c81-397b-4a74-8dff-2fad2fac894b
4. KMS Client Key:
   http://technet.microsoft.com/en-us/library/ee624355.aspx#section2_3

How to Install & Configure KMS (Key Management Service) - Server 2008

Requirements:

1. You need 1 KMS host/server -Windows Server 2008 R2 or Windows 7
2. You need 25 clients Windows7 client or 5 Windows Server 2008 client
3. Windows7 client KMS Setup Key
   http://technet.microsoft.com/en-us/library/ff793421.aspx
   
   

   Windows 7 and Windows Server 2008 R2
   Windows 7 Professional	FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4

   
   
   
   
4. MS Office 2010 Professional KMS Setup Key
   http://technet.microsoft.com/en-us/library/ee624355.aspx#section2_
   3
   
   

   MS Office Suit 2010 Client Key
   Office Professional Plus 2010	VYBBJ-TRJPB-QFQRF-QFT4D-H3GVB

5. Update Windows KMS Host(Windows Server R2) and KMS Client(Windows7) & Restart both of them
6. Allow TCT port:1688 and Key Management Service in Windows Firewall

What to avoid:

1. There is a difference between Windows7 KMS key and Windows7 KMS setup key. Do not install Windows7 KMS key on the Windows7 Client. 
2. You do not need a Volume Activation Management Tools - VMAT for KMS Installation & Configuration.

Setup Windows Server R2 as KMS Server/Host:

1. Download & Install the update - KB968912.
2. Run command promt as Administrator, type the following command and press enter
   slmgr /ipk windows7_KMS_Key
3. Type the following command and press enter to activate the KMS host:
   slmgr /ato
4. Type the following command and press enter to see what mode KMS is running and status:
   slmgr /dlv 
5. Type the following command and press enter stop & restart the software licensing service:
   net stop slsvc
   net start slsvc
6. To setup KMS office Host
    To trigger activation manually on the KMS client, runospp.vbs /act

Setup KMS Client:

1. Run command promt as Administrator, type the following command and press enter:
   slmgr /ipk windows7_KMS_Setup_Key
2. Type the following command and press enter to see what mode KMS is running and status:
   slmgr /ato
3. Type the following command and press enter to see what mode KMS is running and status:
   slmgr /dlv 

Troubleshooting:

Problem:

If you run the command slmgr /ipk windows7_KMS_Key in the Windows7 client PCs then all PCs will become KMS server or KMS host. 

Solution:

In order to make Windows7 as KMS client 

1. Run command promt as Administrator, type the following command and press enter:
   slmgr /rearm
2. Type the following command and press enter:
   slmgr /ipk windows7_KMS_Setup_Key

Problem:

KMS client cannot find the KMS host.

Solution:

To manually create a KMS SRV record in a Microsoft DNS server

1. On the DNS server, open DNS Manager. To open DNS Manager, click Start, click Administrative Tools, and then click DNS.
2. Click the DNS server on which you need to create the SRV resource record.
3. In the console tree, expand Forward Lookup Zones, right-click the domain, and then click Other New Records.
4. Scroll down the list, click Service Location (SRV), and then click Create Record.
5. Type the following information:
• Service: _VLMCS
• Protocol: _TCP
• Port number: 1688
• Host offering the service: <FQDN_of_KMS_Host>
6. When you are finished, click OK, and then click Done.

Set the permission on the DNS Server to allow updates by members of the KMS host security group.

What it means is right-click the initial, your first KMS host in DNS under _tcp, select Properties and under the security tab, add the newly created security group and give it full control. Reboot second kms host server and the DNS will update with a new _VLMCS record.

- Set the permissions for the SRV group to allow updates by members of the
global security group


Test the KMS server configuration on Client Machine

The KMS server should publish its SRV records in your domain DNS, you should verify that these records exist.
Open C:\Windows\system32 and execute the following command

nslookup -type=srv _vlmcs._tcp

ipconfig /all

If you run /remhst, then /act, then /dhistorykms, is there a list of machines that are tried?

You should see output similar to the following:

Quote

DNS request timed out.

timeout was 2 seconds.

Server: UnKnown

Address: 192.168.3.1

_vlmcs._tcp.windows-noob.local SRV service location:

priority = 0

weight = 0

port = 1688

svr hostname = sccm2007.windows-noob.local

sccm2007.windows-noob.local internet address = 192.168.3.1

Troubleshooting:

SLMGR.VBS

From an elevated command prompt, type SLMGR.vbs /dlv. This will give you verbose output of the Software Licensing service. The screenshot below is from my machine, a KMS client within Microsoft.

Problem: Suddenly KMS server client count has gone down:
Solution:
1. Just rearm 25 pcs and restart.

Reference:

1. http://www.windows-noob.com/forums/index.php?/topic/649-how-can-i-setup-a-kms-server/
2. http://sysadministrivia.blogspot.com/2010/07/windows-kms-setup-keys.html
3. Troubleshooting: http://technet.microsoft.com/en-us/library/ee939272.aspx#EFAA