Jul 27 2009

GPO Folder Redirection Failing after moving FileServers

ISSUE
====

GPO folder redirection not working.

Domain: Windows 2003
Clients: Windows XP, Windows Vista, Windows 7

ERROR
=====

On the client machines:

Log Name:      Application
Source:        Microsoft-Windows-Folder Redirection
Date:
Event ID:      502
Task Category: None
Level:         Error
Keywords:      Classic
User:
Computer:
Description:
Failed to apply policy and redirect folder “Documents” to “\\NEW SERVER\UsersMyDoc\USER NAME>\My Documents”.
Redirection options=80009211.
The following error occurred: “Failed to build the list of regular subfolders under “\\OLD SERVER\UsersMyDoc\\My Documents”".
Error details: “Logon Failure: The target account name is incorrect.
“.

And

Log Name:      Application
Source:        Microsoft-Windows-Folder Redirection
Date:
Event ID:      510
Task Category: None
Level:         Warning
Keywords:      Classic
User:
Computer:

Description:
Folder redirection policy application has been delayed until the next logon because the group policy logon optimization is in effect.

On the Server:

Event Type: Error
Event Source: Folder Redirection
Event Category: None
Event ID: 103
Date:
Time: 16:46:17
User: N/A
Computer:
Description:
Failed to perform redirection of folder . The fully expanded paths for the folder could not be determined. The following error occurred:
The system could not find the environment option that was entered.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

ISSUE
====

One of the main reasons for the group policy folder redirection failing is  due to the existing folder redirection. What appears to happen is that the system determines if the users folder redirection was already enabled, if the folder was already being redirect it will access the old share and then migrate all of the data to the new share, in this example the file server no longer existed.

SOLUTION
========

Create a new group policy, for example called “Apply Folder Redirect Reg”

Link the GPO to the relevant OU’s, where folder redirection is failing

with in the ou create a new logon script (under the user container)

create a batch file in the following location \\DOMAIN CONTROLLER\NETLOGON\Policy_Reg.bat

batch file to contain the following


REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" /v Personal /t REG_EXPAND_SZ /d "\\NEW SERVER\UsersMyDoc\%USERNAME%\My documents" /f


REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" /v Personal /t REG_SZ /d "\\NEW SERVER\UsersMyDoc\%USERNAME%\My documents" /f

REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" /v "My Pictures" /t REG_EXPAND_SZ /d \\NEW SERVER\UsersMyDoc\%username%\My documents\My Pictures" /f

REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" /v "My Pictures" /t REG_SZ /d "\\NEW SERVER\UsersMyDoc\%username%\My documents\My Pictures" /f

REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" /v "My Video" /t REG_EXPAND_SZ /d "\\NEW SERVER\UsersMyDoc\%username%\My documents\My Video" /f

REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" /v "My Video" /t REG_SZ /d "\\NEW SERVER\UsersMyDoc\%username%\My documents\My Video" /f

REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" /v "My Music" /t REG_EXPAND_SZ /d "\\NEW SERVER\UsersMyDoc\%username%\My documents\My Music" /f

REG ADD "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" /v "My Video" /t REG_SZ /d "\\NEW SERVER\UsersMyDoc\%username%\My documents\My Music" /f

Under AD Site and Service replicate settings to all servers.
Run Gpupdate /force on the DC where the GPO was created
Get your users to log off and then log back in again.

Unlink the GPO once you know all users have been updated


Jul 21 2009

MOSS Moving Database Server

There would appear to be many different types of methods to move database servers for the MOSS Databases. the steps below have worked well for me:

  • Build new SQL Server (4xCPU and 4GB RAM) or use exsisting
  • Enable new SQL Server for TCP/IP and listen to all ports
    • Open SQL Server Configuration Manager

SQLListen 

  • Create security login accounts as on old server on new server (Farm and web app accounts)
    • Either make a note of each user and permissions under Security-Logins
    • Or Script each Security-Logins relating to SharePoint

SQLScriptLogon 

  • Set all MOSS Databases to read-only on existing server.
    • SharePoint_Config.. (should have one)
    • Content.. (should have one or more)
    • AdminContent..(should have one or more)
  • Backup all MOSS Databases on existing server.
    • SharePoint_Config.. (should have one)
    • Content.. (should have one or more)
    • AdminContent..(should have one or more)
  • Restore all MOSS Databases to new server
    • SharePoint_Config.. (should have one)
    • Content.. (should have one or more)
    • AdminContent..(should have one or more)
  • On all MOSS Servers (WFE, QUERY, INDEX) Start the SQL Server Native Client Network Utility (%SYSTEM%\cliconfg.exe), then run through the following:
  1. On the General tab, verify that TCP/IP is enabled.
  2. On the Alias tab, click Add.
  3. Repeat steps a through f on all servers that connect to SQL Server.
  4. The Add Network Library Configuration dialog box appears.
  5. In the Server alias box, enter the name of the existing\old instance of SQL Server.
  6. In the Network libraries area, click TCP/IP.
  7. In the Connection parameters area, in the Server name box, enter the new server name and instance to associate with the alias, and then click OK.

MOSSMOVEDBSERVER

UPDATE 27-Oct-2009: Added some more pictures


Jul 20 2009

ProClarity 6.0 – 6.3 Changing OLEDB Provider from Analysis Services 2000 to 2005

Step 1 – Configure Analysis Services 2005 for remote connections:

Open analysis services, please perform the following steps:
- All programs\Microsoft SQL Server 2005\Configuration Tools\Sql Server Surface Area Configuration
- Click on the Surface Area Configuration for Services and Connections
- Select Remote Connections under the MSSQLSERVER\Analysis Services node
- Make sure that Local and Remote connections is selected (to allow remote connections)

Restart the SQL Analysis Service 2005.

Step 2 – Install OLEDB Provider for SQL Analysis 2005:

Download and Install the following on the ProClarity server

X86 Package (SQLServer2005_ASOLEDB9.msi) – 12160 KB
X64 Package (SQLServer2005_ASOLEDB9_x64.msi) – 27981 KB
IA64 Package (SQLServer2005_ASOLEDB9_ia64.msi) – 34700 KB

Step 3 – Change the OLEDB Provider:

Logon to the ProClarity server:
- Launch the ProClarity Professional client,
- go to menu bar select File -> Options,
- change your MSOLAP provider via the OLAP provider tab.