Please review my migration plan for moving Forest from W2K to W2K3

Discussion in 'Server Migration' started by Bill-MT, Jun 22, 2005.

  1. Bill-MT

    Bill-MT Guest

    My Steps to Migrate W2K forest to W2K3
    =======================================

    1) Notify Desktop Coordinators of SMB/CIFS - SMB signing issue. Unless
    someone reports a problem with this no change is necessary. If there is a
    problem (with say the SAMBA servers in our network), may need to DISABLE smb
    service signing in Domain Controllers Policy. (see step 16 below).

    2) Make sure all DCs are Windows 2000 sp4 - done. (three in Root domain,
    four in User domain)

    3) Verify replication throughout the forest. Use 2003 version of REPADMIN,
    so first install 2003 member server with tools. Verify Largest Delta in
    column (see appropriate KB notes).

    4) Remove non-existent W2K DCs - those were previously Demoted but are still
    referenced by some AD tools and by NetIQ tool even though they no longer have
    NTDS data listed in AD Sites & Services tool. (see KB216498)

    5) Remove any non-existent external trusts via AD domains & trusts tool.

    6) Use HEALTHCHECK (on W2K3 support tools) and DCDIAG to test SYSVOL/FRS
    replication.

    7) Use DCDIAG or NETDOM to check FSMO roles.
    a. When building replacement for current Schema/DomainName/RootPDC
    machine, make sure Domain Naming master is a GC.
    b. Keep Domain Naming and Schema master together.
    c. Keep RID and PDC together.

    8) Use REPADMIN to check inbound replication

    9) Find out what to do with DNS scavenging.
    (scavenging option is currently not-set on any of the MS-DNS servers).

    10) Distributed Link Tracking - how can I tell if we are using this?

    11) Do SYSTEM STATE backups on all DCs before proceeding.

    12) Run InetOrgPersonPrevent.ldf _BEFORE_ w2k3 ADPREP.
    --> CRITICAL. - wait for replication.

    a. this is necessary because Exchange 2000 was added to W2K forest/domain
    without first doing InetOrg fix.
    b. should this be done "after hours" because of replication load issues
    on DCs or
    Exchange servers?

    13) Run adprep /forestprep on SCHEMA master - wait for replication.
    (login as SCHEMA ADMIN)
    a. Ignore 1153 errors if they occur.
    b. Verify changes have replicated.
    c. Look for mangled LDAPDisplayNames (should not be mangled if
    InetOrgPersonPrevent.ldf done first).
    d. Assuming adprep runs without interruptions, anything to worry about
    here?

    14) Run adprep /domainprep on INFRASTRUCTURE master - wait for replication.
    (login as DOMAIN ADMIN).
    a. Must be done on BOTH (Root and User) domain infrastructure masters.
    - wait for replication.
    b. Done just once on each INFRASTRUCTURE master.
    c. Can upgrade member servers anytime (not part of forest upgrade).
    d. Assuming adprep runs without interruptions, anything to worry about
    here?

    15) After ADPREP run and all changes replicated.
    a. PROMOTE a NEW W2K3sp1 member server then MOVE the following Roles.
    - First DC must have following roles:
    Domain Naming & PDC of Forest Root (must also be a GC for
    Dom Name master role).
    - And remember - First DC in user domain must be the PDC of that
    domain.
    b. Install any newly required hotfixes
    (check windows update again now that machine is DC).
    c. Any problems using the Promotion (DCPromo) method
    rather than Upgrade method? {I don't like upgrades}.

    16) If SMB-signing an issue - disable SMB service signing
    after first W2K3 DC introduced.
    a. can be done via Domain Controller policy.

    17) Verify health of upgrade by checking - DC replication and server event
    logs.
    a. IGNORE event id: 1913

    18) Install w2k3 adminpak.msi and suptools.msi on each new W2K3sp1 server.
    19) Make new system state/drive backups after each server promotion & role
    move.

    20) Perform off-line defragmentation
    - 24hours after SIS event ID 1966 shows completion. (optional).

    21) Check DLT service to see if disabled on new server.
    - Will this break anything, how can I tell if my forest uses DLT
    objects?

    22) Perform off-line defrag 60+ days after upgrade (optional).

    23) Keep Forest at functional level zero -
    because running Exchange 2000 - Recipient Update Service issues.
    a. Remember to change SERVERS designated as recipient update server as
    new DCs are added & old ones removed.

    24) Raise Domain functional levels after all domain DCs are running W2K3sp1.
    a. Any Exchange Server 2000 issues with raising domain functional levels?

    25) Anything I've forgotten here?

    Note: this migration plan was build using KBs referenced in KB555040
    (common mistakes when upgrading) and KB325379 (how to upgrade).
     
    Bill-MT, Jun 22, 2005
    #1
    1. Advertisements

  2. Hello Bill,

    Good to hear from you.

    According to the message, I understand that you want to upgrade you win2k
    forest to win2k3 forest using new win2k3 servers. Please correct me if I am
    off base.

    After reviewing the whole plan, I have the following question.

    Is Exchange2k installed on a member server or a DC?
    Generally speaking, Exchange2k on member servers will not affect domain
    function level. Please be sure that Exchange2k cannot be installed on a
    win2k3 server. It is ok to be located in a win2k3 domain.

    As for the DLT, please check the following article.

    Distributed Link Tracking on Windows-based domain controllers
    http://support.microsoft.com/default.aspx?scid=kb;en-us;312403

    According to the article, Distributed Link Tracking objects are replicated
    among all domain controllers in the domain that is hosting the computer
    account and all global catalog servers in the forest. The Distributed Link
    Tracking Server service creates objects in the following distinguished name
    path:

    CN=FileLinks,CN=System,DC=domain name container of Active Directory

    So we can use Adsiedit to check the above entry and then make sure whether
    the win2k forest has used DLT.

    Adsiedit
    ===================
    To open Adsiedit, please click Start, point to Programs, click Windows 2000
    Support Tools, click Tools, and then click ADSI Edit.

    Note If the Windows 2000 Support Tools are not installed, install them from
    the Windows 2000 CD. The file path is <CDROM Drive>:Support\Tools\Setup.exe.

    Regarding your plan, since they are taken from the published KB articles, I
    have no concerns. I would like to give you some suggestions.

    Step 13. If you want to roll back the upgrade process, you can disconnect
    the DC with the network, run forestprep and then connect it back. This way,
    the extended schema will not be replicated to other DCs in the process. If
    you have no plan to roll back the process, just ignore what I said.

    Step 15. It is ok to promote a new win2k3 member server.

    Step 20. Since the step is an optional step which is performed on the
    domain controllers that you upgraded to Windows Server 2003, if you don't
    upgrade original win2k DCs, there is no need to do this step.

    Step 21. The service is disabled on win2k3 server by default.

    Please check the following article.

    812519 Services That Are Turned Off by Default in Windows Server 2003
    http://support.microsoft.com/?id=812519

    Step 23. Recipient Update Service is part of Exchange service. Regarding
    this part, I would like to suggest that you post in the Exchange newsgroup:
    microsoft.public.exchange.setup for most accurate information.


    Hope this helps. If you have further concerns, please feel free to get in
    touch!

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Frances [MSFT], Jun 23, 2005
    #2
    1. Advertisements

  3. Bill-MT

    Bill-MT Guest

    My E2K servers are all members servers.
    My DCs are just DCs (no layered apps or other functions).
    Thanks, I had read the stuff, but must have missed the DN path to check
    in all the reading. I'll check the path listed above and let you know if I
    have further questions.
    I have only modified the schema twice (once as part of the original W2K
    install/ migration from NT and the second time to install E2K. Thus with so
    little background doing schema modifications and the hugh number of warnings
    MS puts out about breaking the forest if ADPREP (schema modification) goes
    wrong. I'm just looking for some mental hand holding here. (I don't want
    the schema to break because I'm doing something stupid here - like running
    ADPREP at the wrong time of day or forgetting to do something - something
    that is obvious to you but not to me).


    Additional clarification:

    I have only one new piece of hardware, thus I intend on doing what MS calls
    a "swing" upgrade (at least in Exchange terms that's what it's often called).
    That is you use the new piece of hardware to create a new W2K3sp1 DC, move
    the roles from an old DC to it, demote and remove that old DC, rebuild it as
    a new W2K3sp1 DC, move roles from another original DC to it, demote/remove
    that old DC, rebuild it, move roles from another to it, etc, etc.

    I realize this takes "much" more time than just 'upgrading' my current DC's
    however, I also know that with this method each machine is running a stable,
    clean, fully patched install of W2K3sp1 before it's committed to being a new
    DC in the forest/domains.

    I'll wait at least one day between each schema modification: first the
    InetOrgFix, and then each ADPREP run (.i.e /forest , then /domain for Root
    domain, then /domain for User domain) so the schema mod or ADPREP process
    will take at least four days itself.

    I'll also wait at least one day for replication to occur between "each"
    Promotion, role move and Demotion activity (Thus doing each new server will
    take at least three days).

    If you can think of any other procaution I need to take using this method,
    please let me know.

    This seems to me to be the most conservative and safest way to do the upgrade.
     
    Bill-MT, Jun 23, 2005
    #3
  4. Hello Bill,

    Thanks for the detailed information.

    It is best to wait till the replication of the changes is broadcasted to
    the whole forest. You seem to be very careful to wait a day for each change.

    As for the "swing" upgrade you mentioned, I have only one concern. Is there
    any need that we move roles again and again? I assume the role refers to
    FSMO roles.

    Basically speaking, only a few DCs hold FSMO roles. If all the FSMO roles
    are held on one DC, we only have to move roles once to the first new win2k3
    DC.

    The other suggestions I think of are listed as follows.
    1. Please install AD-integrated DNS on the new win2k3 DC, this process will
    auto replicate DNS from 2k to 2k3.
    If the clients are pointing to an old DC for DNS server, please configure
    all the clients to point to the new win2k3 DC, since you may "upgrade" that
    old DC one day.
    Please note: DCs and member servers are also DNS clients.

    2. Make the new server a GC.

    3. Add DHCP role to the new server.

    Please refer to the following KB:

    130642 How to Move a DHCP Database to Another Windows Server
    http://support.microsoft.com/?id=130642


    Hope this helps. If you have further concerns, please get in touch.

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Frances [MSFT], Jun 24, 2005
    #4
  5. Bill-MT

    Bill-MT Guest

    Basically speaking, only a few DCs hold FSMO roles. If all the FSMO roles
    Sorry I confused you I'm not moving roles over and over. I'm just rebuild
    "each" server (one at a time) mostly re-using existing hardware and moving
    the "existing" roles on "the" server "to be replaced" to the new replacement
    server. This could be a lot of roles (RootSrvA for example has
    GC,RootPDC,DomNam,Schema,RID) or no roles depending on the particular DC.

    W2K3-RootSrvA (new hardware) - gets the roles W2K-RootSrvA current has.
    W2K-RootSrvA removed.

    W2K3-RootSrvB (re-use hardware) - get roles W2K-RootSrvB currently has.
    W2K-RootSrvB removed.

    W2K3-RootSrvC (re-use hardware) - gets roles W2K-RootSrvC currently has
    W2K-RootSrvC removed

    -now I move to user domain--

    W2K3-UserSrvA (re-use hardware) - gets roles WK2-UserSrvA currently has.
    W2K-UserSrvA removed....

    I continue this until pattern until I have redone (upgraded) all W2K
    DCs...A,B,C,D in User domain.

    Is it critical that the DNS servers for the forest are running W2K3 right
    away. The current DNS/WINS servers for the forest are UserSrvC and UserSrvD
    and are the last I had planned on upgrading. As long as I intend on leaving
    my Forest at level zero and domains at W2K native until all DCs are done, is
    it truly necessary for me to have W2K3 DNS servers right away?

    Also my domains have discontiguous name spaces. User domain is NOT a child
    of the root. [as in: ROOT.LOCAL and USER.LOCAL not: ROOT.LOCAL and
    CHILD.ROOT.LOCAL]. Root domain was build only to separate out Schema so
    default admins would not have default access to schema mods. No user
    accounts exist in the Root domain.

    Also I only have one [the default] site.
    please let me know. - bill
     
    Bill-MT, Jun 24, 2005
    #5
  6. Hello Bill,

    Thanks for the detailed information.

    I understand your "swing" upgrade. It is always best to use a clean
    installed machine.

    As for the DNS part, it is not necessary to configure it on a win2k3 DC at
    once. Please don't forget it when you upgrade the last 2 DCs. Using
    AD-integrated DNS is always recommended.

    As for the last 2 concerns, I think they will not affect the upgrade plan.

    Hope this helps. Further concerns, please get in touch!

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Frances [MSFT], Jun 27, 2005
    #6
  7. Bill-MT

    Bill-MT Guest

    [Frances:] Tracking Server service creates objects in the following
    distinguished

    Frances, I used ADSIedit over the weekend to look at the DN path listed
    above. Surprisingly it has thousands of link entries. I didn't know
    anything was using DLT.

    The KB article appears to be just a reference on how to remove (clean up)
    these links in the AD but it doesn't mention what might break because the DLT
    service goes from a running to disabled state with the migration.

    Will I need to 're-enable' this service after the migration for any reason?
    What kind of errors or failed functionality would I look for to know that the
    service needs to be re-enabled after I start the migration?

    thanks for your time on this. - bill.
     
    Bill-MT, Jun 27, 2005
    #7
  8. Hello Bill,

    Thanks for the reply.

    You mentioned there are many entries listed. I suggest that you check one
    entry and make sure what it is.

    As for reenabling the service, please check the article below. After a
    careful review of the article, I think we recommend turning off the
    Distributed Link Tracking Server service on all domain controllers, and
    deleting Distributed Link Tracking objects from Active Directory domain
    controllers.

    Please have a check.

    312403 Distributed Link Tracking on Windows-based domain controllers
    http://support.microsoft.com/?id=312403

    So I recommend not enabling the service again. You may decide what to do
    based on your real environment.

    Hope this helps. Any concern, please get in touch!

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Frances [MSFT], Jun 28, 2005
    #8
  9. Bill-MT

    Bill-MT Guest

    Frances,

    Thanks for the info on DLT, I revewed the kb one more time after your
    reference and now feed comfortable with that process.

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

    Looking through the message stream the only topic we have not covered in any
    detail is DNS scavenging. By default it is evidently disabled (not set) on
    my DNS servers (by the way, my forest DNS zones are already AD-Intregrated,
    if I didn't mention that before).

    Can you give me any additional information on what I should do if anything
    on this topic. The migration bulletin recommends starting DNS scavenging 60
    days before start of migration. Well, I'm not going to meet that requirement.

    Should I enable 7 day DNS scavenging as indicated in the migration document
    (KB325379)?

    If I do will it have any negative effects on the Forest/Domain that I should
    be aware of/prepare for?

    thanks again for your time and efforts here. - bill.

    (scavenging option is currently not-set on any of the MS-DNS servers).
     
    Bill-MT, Jun 28, 2005
    #9
  10. Hello Bill,

    Thanks for the reply.

    I understand that your concern is the DNS scavenging settings. It is the
    optional step in the KB article. Generally speaking, this will not affect
    the upgrade process.

    You can set it and wait for 7 days as the article suggests. The setting
    means that if the DNS server cannot detect an entry for 7 days, the entry
    will be deleted. That way, the aged DNS objects will be cleared.

    For more information, please take a look at the "Aging and Scavenging"
    section of the DNS Whitepaper available at
    http://www.microsoft.com/WINDOWS2000/techinfo/howitworks/communications/name
    adrmgmt/w2kdns.asp

    Hope this helps. Any other concerns, please get in touch!

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Frances [MSFT], Jun 29, 2005
    #10
  11. Bill-MT

    Bill-MT Guest

    Frances, I was just informed by one of the SAMBA groups on campus that they
    are having trouble migrating to a version that supports SMB-signing. I have
    the following step in my plan.

    16) If SMB-signing an issue - disable SMB service signing
    after first W2K3 DC introduced.
    a. can be done via Domain Controller policy.


    It now appears that I "will" at least for a while need to disable
    SMB-signing... So

    1) Do I need to disable SMB signing after I install the first W2K3 server as
    I indicated above. As you know the first three DCs replaced will be in the
    Root Domain not the User Domain where the SAMBA clients are located. So do I
    still need to disable this after the first W2K3 promotion? Do User domain
    clients ever contact Root domain controllers? Can I wait to disable
    SMB-signing until I do the first User domain controller promotion and then
    only do it for the User domain?

    2) Assuming that I change the SMB-signing setting by changing the "Domain
    Controller Policy". Can I assume that I do the same thing in reverse to
    eventually "re-enable" SMB signing in the domain.

    thanks for your help. - bill
     
    Bill-MT, Jun 29, 2005
    #11
  12. Hello Bill,

    Thanks for the reply.

    According to the message, I understand that you are concerning the SMB
    signing.

    As we see in the article 325379, if some network clients that use the
    SMB/CIFS protocol will access shared files and printers in the Root Domain,
    we have to disable SMB signing on it.

    I understand that the 2 domains you mentioned are under the same forest.
    Root domain is the forest root domain, and User domain is the tree root
    domain. Is this correct?
    By default, the 2 domains have a Two-way trust. You can check this to make
    sure. So User domain clients may contact Root domain controllers to access
    the shared files and printers in Root domain. You may decide whether to
    disable SMB signing based on your real environment. If you are sure User
    domain clients will not use the resources in the Root domain, we can
    disable SMB signing on the User domain only.

    Please refer to the following article for more information about SMB
    signing.

    Overview of Server Message Block signing
    http://support.microsoft.com/default.aspx?scid=kb;en-us;887429


    As for the 2nd question, I think the reverse step should reenable SMB
    signing.


    In addition, I have found the following article which addresses some issue
    when disabling SMB signing. You may have a check.

    You cannot open file shares or Group Policy snap-ins when you disable SMB
    signing for the Workstation or Server service on a domain controller
    http://support.microsoft.com/default.aspx?scid=kb;en-us;839499


    I believe that there will always be a lot to consider before we perform the
    real upgrade. However, please understand that our newsgroup is focused on
    break/fix issues. If you have related break/fix issue in the real process,
    please post back in the newsgroup, since we will never cover all the issues
    beforehand due to the complicated real network environment.

    Your understanding and cooperation on this will be greatly appreciated.

    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.
     
    Frances [MSFT], Jun 30, 2005
    #12
  13. Bill-MT

    Bill-MT Guest

    Thanks much for your answers and your focus on those answers...

    It doesn't matter to me much if I ask Ten separate questions or ask Ten
    sub-questions as long as either helps me to get my job done.

    I also believe it a better use of time to 'ask' first than to spend more
    time 'digging out' later.

    So I'll talk with MS-Technet about how they can make these newsgroups better
    geared to that approach. In just browsing the newsgroup entries, I agree
    that most of the posts are focused in that direction. Maybe that's why MS
    and MS products get such a bad reputation... a reactive rather than proactive
    attitude toward problem resolution.

    have a good weekend.
    And thanks again for all your support, it's been most helpful....! - bill.
     
    Bill-MT, Jun 30, 2005
    #13
  14. Hello Bill,

    Thanks for your understanding on this issue.

    As for your concern regarding the policy of our newsgroup, you may share
    your feedback with the Technet team.

    If you have any break/fix issues in the upgrading process in the future,
    please feel free to post in the newsgroup.


    Best regards,

    Frances He

    Microsoft Online Partner Support

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================
    Business-Critical Phone Support (BCPS) provides you with technical phone
    support at no charge during critical LAN outages or "business down"
    situations. This benefit is available 24 hours a day, 7 days a week to all
    Microsoft technology partners in the United States and Canada.

    This and other support options are available here:
    BCPS:
    https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
    Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

    If you are outside the United States, please visit our International
    Support page: http://support.microsoft.com/common/international.aspx.
    =====================================================
    This posting is provided "AS IS" with no warranties, and confers no rights.

    ============================================================================
    ===================
    In an effort to secure NNTP access to partners only, the password will
    change every 6 months when using Outlook Express or other NNTP client to
    view the Microsoft Managed Newsgroups. The current password has been active
    since July 1, 2005.

    This does not impact the web-based newsreader at:
    https://partner.microsoft.com/global/technicalsupport/registeredsupport/4001
    3938

    The new password will be active from July 1, 2005 until January 3, 2006
    (9:00 am PST).

    Please visit and mark as a favorite the following link to obtain the new
    password information as well as the instructions for configuring OE for
    newsgroup access.
    https://partner.microsoft.com/global/40012653. You will need to sign in to
    the partner portal to access this page.
    ============================================================================
    =====================
     
    Frances [MSFT], Jul 4, 2005
    #14
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.