• How to Reset Windows 7 WMI

    Currently, we have no script to rebuild WMI in Windows 7 client. Following is the procedure to rebuild WMI in Windows 7.

      1) Perform a manual logcopy on the PC.
      2) Open an elevated command prompt.
      3) Verify the WMI repository is not corrupt by running the following command:

          winmgmt /verifyrepository

    If the repository is not corrupted, a “WMI Repository is consistent” message will be returned. If you get something else, go to step 4.

    4) Run the following commands:   

    winmgmt /salvagerepository

    If the repository salvage fails to work, then run the following command to see if it resolves the issue:
    winmgmt /resetrepository

    After the last command, there should be a “WMI Repository has been reset” message returned.

    NOTE: We always use winmgmt /resetrepository to repair the WMI in the Windows 7 client.

  • SCCM Backup Fail

    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

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

  • Error encountered when creating Routing Group Connectors between Exchange 2010 and 2003: Active Directory operation failed. The name reference is invalid.

    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

     

     

  • NTBACKUP單捲磁帶滿時,如何在不重新建立Job變更磁帶名稱


     


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

     

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

     

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

     

    首先為新磁帶命名

     

    我們的做法是:

     

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

     

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

     

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

     

    clip_image001

     

    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中測試,只有通過新增的方式,對新磁帶進行命名。 請客户確認是否有其他硬,工具,或者其他軟體方式對磁帶進行命名。

     

     

  • Client cannot connect to Windows 2003Terminal

    錯誤訊息:

    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"刪除,刪除後重新開機