問題描述︰
Using W2K8 remote app, WinXP client cannot  redirect print
======================================
當您使用W2K8 的Remote App 功能，而Client 目前有Windows 7, Windows Vista & Windows XP SP2三種作業系統。
而您發現當Windows XP SP2 client 使用Remote App想要列印文件時，無法看到本機redirect 的local printer，但是Windows 7 & Windows Vista client 並不會有這樣的問題。
======================================

建議與解決方案︰
我想您的W2K8環境應該有啟用Easy printer功能，如果您並沒有特別在W2K8 TS server上安裝Client 端的printer driver(以往如果要RDP到W2K3的TS server, 您必須要在W2K3上安裝相應的Printer driver, 才支援將Client 已連線的printer, redirect 成功), 但是Windows 7 & Windows Vista client 即可直接redirect printer, 這說明應該有啟用W2K8的Easy printer功能。而這也將間接說明為何您的Windows XP client 無法redirect printer成功，因為Windows XP要能做用Easy printer的功能，有一些基本的要求如下:

==================================================

To use the Terminal Services Easy Print driver, clients must be running both of the following:

• Remote Desktop Connection (RDC) 6.1

• At least Microsoft .NET Framework 3.0 Service Pack 1 (SP1)

The following list provides information about which operating systems support the Terminal Services Easy Print driver, and whether additional configuration is required.

• Windows Vista® with SP1 includes both of the required components. By default, Windows Vista with SP1 supports the Terminal Services Easy Print driver with no additional configuration.
• Windows XP with Service Pack 3 includes RDC 6.1. However, you must install a supported version of .NET Framework separately. You can download Microsoft .NET Framework 3.5 (which includes .NET Framework 3.0 SP1) from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=109422).

==================================================
根據以上官方文件的建議，要能夠成功的在Windows XP上redirect printer，您必須將Windows XP的Client 升級到SP3的版本並且另外安裝.NET Framework 3.0 SP1元件。

PS.上述.NET Framework 3.0 SP1連結, 是.NET Framework 3.5版本, 並包含.NET Framework 3.0 SP1.

參考資訊連結︰
Terminal Services Printing
http://technet.microsoft.com/en-us/library/cc753853(WS.10).aspx

How to enable easy print?
=================================
What settings have been added or changed in Windows Server 2008?

Group Policy settings

The following Group Policy settings have been added for Terminal Services printing:

• Use Terminal Services Easy Print printer driver first
  This policy setting is located in the following node of the Local Group Policy Editor:
  Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection
  The possible values are:

· Enabled or Not configured: If this policy setting is enabled or not configured, the terminal server will first try to use the Terminal Services Easy Print driver to install all client printers. If for any reason the Terminal Services Easy Print driver cannot be used, a printer driver on the terminal server that matches the client printer will be used. If the terminal server does not have a printer driver that matches the client printer, the client printer will not be available for the Terminal Services session. By default, this policy setting is not configured.

· Disabled: If you disable this policy setting, the terminal server will try to find a suitable printer driver to install the client printer. If the terminal server does not have a printer driver that matches the client printer, the server will try to use the Terminal Services Easy Print driver to install the client printer. If for any reason the Terminal Services Easy Print driver cannot be used, the client printer will not be available for the Terminal Services session.

• Redirect only the default client printer
  This policy setting is located in the following node of the Local Group Policy Editor:
  Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection
  The possible values are:

· Enabled: If you enable this policy setting, only the default client printer is redirected in Terminal Services sessions.

Disabled or Not configured: If you disable or do not configure this policy setting, all client printers are redirected in Terminal Services sessions. By default, this policy setting is not configured.

SYMPTOM
=========
Wrong day time displayed while the report selection time is over 2010/1/1. 

CAUSE
========================
We have a date Dimension view (SC_DateDimension_View) in the DW database which contains the day definition (such as 2009 12 31). This table is populated with a stored procedure named as "p_populatedateDimesion.sql".
However, we defined a time limit t0 '1/1/2010 12:00 AM' in the stored procedure which means the latest day definition in the date Dimension view will be 2010 1 1. So if the incoming performance data (same to alert, event data) will be linked with a wrong day dimension while DTS job transferring data to the DW DB.

Sample code in the stored procedure:
------------------------
     IF @startDate IS NULL
         SET @startDate = '1/1/1998 12:00 AM'

        IF @endDate IS NULL
         SET @endDate = '1/1/2010 12:00 AM'
------------------------

DECLARE @MaxDate DATETIME
SELECT @MaxDate = MAX([Date]) FROM dbo.SC_DateDimension_View
IF (@MaxDate IS NULL)
BEGIN
    EXECUTE p_PopulateDateDimension
END
ELSE IF (@MaxDate < '1/1/2010 12:00 AM')
BEGIN
    SET @MaxDate = DATEADD(day, 1, @MaxDate)
    EXECUTE p_PopulateDateDimension @startDate = @MaxDate
END
GO

WORKAROUND
========================
As a workaround, we can modify the p_populatedateDimesion stored procedure to adjust the end time to a long value (say: 2020 1 1). Then allow the report be generated with correct date value. I have attached modified stored procedure. We can use the below steps to fix the issue:

1. Backup the current SystemCenterReporting database.
2. Connect to the SystemCenterReporting database, run the content in the p_populatedateDimesion.sql.txt file.
3. Run the below query:
    Exec p_populatedateDimesion @startdate = '1/2/2010 12:00 AM'
4. Run the below query statement to ensure the max date time is 2020 1 1:
    Select * from SC_DateDimension_View order by date DESC
5. Run the content in the fixdate.sql.txt file. This will re-link the performance, alert, event date to the accurate one.
6. Re-run the MOM report to see if the returned date value is correct now.

PROBLEM:
===========
Creating the rule and targeting the computer group

CAUSE:
=========
We cannot directly Target the custom group while creating the rule.

RESOLUTION:
=============
If we want to target the custom group to any rule then we have to First target any built in groups at the time of creating the rule and disable the rule. Then set the override for the custom group.

Regarding the editing the rule, the user must have permission on the built in group that we have selected in the beginning and the customer group.

The permission can be given from Administrator console\user roles

1. Create your group and add the members you wish to monitor.
2. Create your rule/monitor and target it at a suitable class. For example if the machines you wish to monitor are all SQL servers, you can use the SQL Computers class.
3. Ensure the rule/monitor is disabled by default. To do this, click the General tab in the Properties dialog box for the rule or for the monitor in question, then make sure that the Rule is Enabled check box is cleared (not checked).
4. Create an override for the rule/monitor targeted at your group and sets the Enabled property to True. To do this follow these steps:
a. In the Authoring pane in the Operations Console, locate the rule or the monitor.
b. Right-click the rule or the monitor, point to Overrides, point to Override the Rule or to Override the Monitor, and then click For a group.
c. Click the group that you want to use, and then click OK.
d. Click to select the Override check box, and then click True under Override Setting.

問題描述︰
DC authentication issue
-DC generate Event id 675 (0x19) from Win2k8 machine

解決方式︰
這是Windows 2003 和Windows 2008 在驗証協定上設計的不同點，有兩種方式可以避免:
1. We can check "Do not require Kerberos pre-authentication" of User account in AD user & computer console, we will not longer get the same event for users.
We can reference to KB: http://support.microsoft.com/kb/954415/en-us

2. Due to this shows that issue is with pre-authentication from machines. And we identified that issue was only with Vista and Windows 2008 machines and not with Windows XP and Windows 2003 machines.
Because of design change pre-authentication is not forced on Vista and Windows 2008 machines. We forced pre-authentication on Windows Vista machines using following registry value:
HKLM\System\CurrentControlSet\Control\LSA\Kerberos\Parameters
Value Name = DefaultEncryptionType
Type = Reg_DWORD
Value Data = 0x17(23)

[問題說明]: 我要怎麼備份現有的GPO, 然後還原 Default Domain Policy 以及 Default Domain Controller Policy 到預設值.

[操作步驟]:

[備份現有的GPO設定]

1. 使用GPMC來備份現有的GPO

2. 選擇備份的位置後按下備份

3. 備份完成後按下確定

[還原GPO到Default Settings]

1. 先下載 2003 Resource Kits Tools 並安裝在DC

http://www.microsoft.com/downloads/details.aspx?FamilyID=9D467A69-57FF-4AE7-96EE-B18C4790CFFD&displaylang=en

2. 打開命令提示字元後輸入以下指令,並回答兩個 Yes還原

# dcgpofix /ignoreschema

3. 還原後請打開GPMC檢查, 原則上不會動到原本link到OU的GPO,只會還原 Default Domain Policy 和 Default Domain Controller Policy