以下二種狀況都可能發生。

狀況一、特定的Client無法看到任一台電腦的工作排程。

解決方法

將以下紅色的文字copy至notepad，並存成一個reg檔，點二下匯入即可。

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\CLSID\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]
@="排定的工作"
"LocalizedString"="@C:\\WINDOWS\\system32\\mstask.dll,-3408"
"InfoTip"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
  6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
  00,53,00,48,00,45,00,4c,00,4c,00,33,00,32,00,2e,00,64,00,6c,00,6c,00,2c,00,\
  2d,00,32,00,32,00,39,00,32,00,33,00,00,00
"IntroText"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
  6f,00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
  00,53,00,48,00,45,00,4c,00,4c,00,33,00,32,00,2e,00,64,00,6c,00,6c,00,2c,00,\
  2d,00,33,00,31,00,37,00,35,00,33,00,00,00
"{305CA226-D286-468e-B848-2B2E8E697B74} 2"=dword:00000005

[HKEY_CLASSES_ROOT\CLSID\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}\DefaultIcon]
@="C:\\WINDOWS\\system32\\mstask.dll,-100"

[HKEY_CLASSES_ROOT\CLSID\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}\InProcServer32]
@="C:\\WINDOWS\\system32\\mstask.dll"
"ThreadingModel"="Both"

[HKEY_CLASSES_ROOT\CLSID\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}\ShellFolder]
"Attributes"=hex:00,00,00,21

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace\{2227A280-3AEA-1069-A2DE-08002B30309D}]
@="Printers"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace\{D6277990-4C6A-11CF-8D87-00AA0060F5BF}]
@="排定的工作"

狀況二、特定的電腦無法被任何其他電腦看到工作排程分享

解決方法：

在有問題的機器上，請做以下的動作：

1.確認 "Task Scheduler" 服務是有啟動的。

2.確認"Remote Registry" 服務是設定成自動，並且有啟動的。

3.確認以下的機碼存在。如果不存在，請匯入附件的機碼。

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace\
  {D6277990-4C6A-11CF-8D87-00AA0060F5BF}

4. 確認 LOCAL SERVICE 該帳號在  HKLM\SYSTEM\ControlSet001\Control\SecurePipeServers\winreg 機碼上有完全控制的權限。假設沒有的話，請加上LOCAL SERVICE這個帳號，然後給予完全控制的權限。

5. 確認以下機碼是否存在，若不存在就忽略這個步驟。如果存在的話，並且值若為1的話，請改成0

HKEY_Local_Machine\Software\Policies\Microsoft\Windows\Task Scheduler
Value Name: Task Creation
Data Type: Reg_DWORD
Value: 0

錯誤訊息:

You cannot initiate a Remote Desktop Connection because the Windows logon software on the remote computer has been replaced by incompatible software irm64.dll

”您無法初始遠端桌面連線，因為在遠端電腦上的 Windows 登入軟體已經被取代成不相容的軟體irm64.dll。”

原因

根據此訊息有些軟體安裝後會修改預設的設定導致有問題

此狀況看起來是有甚麼軟體或是程序加了一個機碼值，而這個DLL檔案又不存在導致

解決

請您備份下列路徑

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

請將"GinaDll"="irm64.dll"刪除，刪除後重新開機

我們目前測試通過的步驟：

1.       將参數以’/g’，改為’/t’(附加磁帶名)，看job成功執行

2.       將舊磁帶移除，系统加入新磁帶的時候， 將新磁帶的名稱改為舊磁帶的名字。backup job能通過磁帶名則能找到新磁帶，然後執行backup操作，job成功執行

首先為新磁帶命名

我們的做法是：

1.       將新磁帶加入系统後， 執行一次以新增方式的backup動作

2.       在這個動作中，系统會為新找到的磁帶命名。我在此將舊磁帶的名字賦给新磁帶。

下圖中的 ’Media created 3/31/2011 at 2:06 PM’即是舊磁帶的名字

3.       在這一次新增方式執行完畢後， 新磁帶的名字即被置為：’Media created 3/31/2011 at 2:06 PM’

4.       經過測試，我發現命令行的方式不能改變這個名字，故需要一次新增方式為磁帶命名

如何確定磁帶名：

1.       打開文件： C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\backup.log

2.       在成功的backup動作中，會有如下記錄：

Backup Status

Operation: Backup

Active backup destination: test 1

Media name: "Media created 3/31/2011 at 6:05 PM"

Volume shadow copy creation: Attempt 1.

Backup (via shadow copy) of "D: New Volume"

Backup set #3 on media #1

Backup description: "Set created 3/31/2011 at 6:05 PM"

Media name: "Media created 3/31/2011 at 2:06 PM" --- 此即為磁帶名

需要請您做如下確認：

1.       打開NTbackup，選擇‘schedule job’一檔，點擊已經建立的bakcup job。點擊 ’Properties’,將’run’一檔的信息複製：

其内容類似：

C:\Windows\system32\ntbackup.exe backup "@C:\Documents and Settings\bkupuser\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\daily.bks" /n "Monday-Full" /d "Mondays Full Backup" /v:no/r:no /rs:no /hc:on /m normal /j "Mondays Job" /l:f /t "tape-name"

2.       確認磁帶名

3.       測試將job的信息由参數為’/g’，改為/t "tape-name"，並進行備份測試

4.       請您提供您對磁帶命名的方式：即在新加入一卷磁帶後，是如何對這個磁帶命名的。 我們在lab中測試，只有通過新增的方式，對新磁帶進行命名。 請客户確認您是否有其他硬體，工具，或者其他軟體方式對磁帶進行命名。

SYMPTOM

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

You run the following cmdlet and it failed to complete.

CMDLET\>New-RoutingGroupConnector -SourceTransportServers "Server01","Server02" -TargetTransportServers

"Eexch01","Eexch02" -BiDirectional $true -name TW2003-2010 -debug -verbose

Active Directory operation failed on dc.domain.com. This error is not retriable. Additional information: T

he name reference is invalid.

This may be caused by replication latency between Active Directory domain controllers.

Active directory response: 000020B5: AtrErr: DSID-03152392, #1:

0: 000020B5: DSID-03152392, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 78e030df (msExchSourceBridgeheadServers

DN)

+ CategoryInfo : NotSpecified: (0:Int32) [New-RoutingGroupConnector], ADConstraintViolationException

+ FullyQualifiedErrorId : 6C3EB645,Microsoft.Exchange.Management.SystemConfigurationTasks.NewRoutingGroupConnector

VERBOSE: [10:22:19.103 GMT] New-RoutingGroupConnector : Ending processing &

ANALYSIS

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

From the following output, you can see that the object DN of Default SMTP Virtual server is the same on all servers except one.

CN=2,CN=SMTP,CN=Protocols,CN=SERVER02,CN=Servers,…

CN=1,CN=SMTP,CN=Protocols,CN=SERVER01,CN=Servers,…

CN=1,CN=SMTP,CN=Protocols,CN=EEXCH02,CN=Servers,…

CN=1,CN=SMTP,CN=Protocols,CN=EEXCH01,CN=Servers,…

CAUSE

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

This is a known issue with Exchange 2007 and Exchange 2010

Here is a workaround for Exchange 2003 server (it only apply if the Exchange server is not Exchange cluster server)

1. Close Exchange system manager

2. Install windows support tools

3. Open ADSIEDIT.MSC

4. Locate on <Configuration>\services\Microsoft Exchange\<Org Name>\Administrative Groups\<Exchange 2003 AG name>\Servers\<Exchange 2003 servername>\Protocol\SMTP

5. On “CN=2” folder, Right click it and select “Rename”, type “1”

6. Force DC replication and restart SMTP service on the Exchange server

After that , you can add the Exchange 2003 server as source or target of the RGC by below powershell.

Set-routinggroupconnector –identity <name of RGC> -sourceTransportServers < all source transport servers’ FQDN> -TargetTransportServers < all target transport servers’ FQDN>

Note:

1. You need to do for two RGC, because RGC is two ways.

2. You need to retype server’s FQDN on sourcetransporservers or targetTransportServers even though they are added.

WORKAROUND

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

Since your server is a cluster server, we cannot modify the DN to workaround the issue.

修改您之前的 Cmdlet 指令，把 SERVER02 從指令中先移除

New-RoutingGroupConnector -Name TW2010-2003 -SourceTransportServers SERVER01,SERVER02 -TargetTransportServers EEXCH01,EEXCH02 -BiDirectional $true

smsbkup.log

========

Error: Sql Server could not prepare for the Backup. $$<SMS_SITE_BACKUP><週五 二月 11 00:05:48.286 2011 台北標準時間><thread=3444 (0xD74)>

Aborting the backup process. $$<SMS_SITE_BACKUP><週五 二月 11 00:05:48.286 2011 台北標準時間><thread=3444 (0xD74)>

$$<SMS_SITE_BACKUP><週五 二月 11 00:05:48.286 2011 台北標準時間><thread=3444 (0xD74)>

Error: CreateSnapshotSet failed... $$<SMS_SITE_BACKUP><週五 二月 11 00:05:48.317 2011 台北標準時間><thread=3444 (0xD74)>

STATMSG: ID=5047 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCMComputerName SITE=SiteCode PID=4352 TID=3444 GMTDATE=週四 二月 10 16:05:48.317 2011 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SITE_BACKUP><週五 二月 11 00:05:48.317 2011 台北標準時間><thread=3444 (0xD74)>

SMS site backup failed. Please see previous errors. $$<SMS_SITE_BACKUP><週五 二月 11 00:05:48.317 2011 台北標準時間><thread=3444 (0xD74)>

解決方法

1.Reinstall sqlwriter.msi on SQL Server then reboot Server

2.We noticed the remote SQL server does not have the SMS_Site_SQL_Backup_ComputerName service. From the site system status on the SCCM console, we noticed the SMS_Site_SQL_Backup component is in critical status. It is trying to reinstall this component.

The sitecomp.log shows following information.

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

Reinstalling component SMS_SITE_SQL_BACKUP...     SMS_SITE_COMPONENT_MANAGER     31/03/2011 10:30:06 AM                12932 (0x3284)

STATMSG: ID=1018 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_SQL_BACKUP_ ComputerName " SYS= ComputerName SITE=SiteCode PID=3232 TID=12932 GMTDATE=Thu Mar 31 02:30:06.256 2011 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER                31/03/2011 10:30:06 AM               12932 (0x3284)

      Starting bootstrap operations...          SMS_SITE_COMPONENT_MANAGER     31/03/2011 10:30:06 AM               12932 (0x3284)

Component file list item in the install map for component SMS_SITE_SQL_BACKUP does not contain srvboot.exe.                SMS_SITE_COMPONENT_MANAGER     31/03/2011 10:30:06 AM               12932 (0x3284)

Bootstrap operations aborted.            SMS_SITE_COMPONENT_MANAGER     31/03/2011 10:30:06 AM               12932 (0x3284)

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

We collected the install.map and check it.

Action Plan

==========

Please modify<InstallPath>Program Files\Microsoft Configuration manager\ install.map as following:

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

BEGIN_COMPONENT_FILELIST

    <SMS_SITE_SQL_BACKUP>

    <1193>

    BEGIN_DIRECTORY

        <bin\i386>

        <9><X86><>

        FILE <smssqlbkup.exe><1><765280>

        FILE <srvboot.exe><0><333664>

    END_DIRECTORY

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