Use Outlook 2003 from SBS2003 \\servername\ClientApps\outlook2003

Discussion in 'Windows Small Business Server' started by PR, May 16, 2007.

  1. PR

    PR Guest

    Anyone,

    Having tried and failed, I ask:
    Is it possible to install Outlook 2003 from the
    (\\servername\ClientApps\outlook2003\setup.exe
    Having tried and faiHaving tried and failed, I ask:
    Can I use Outlook 2003 from SBS2003 on computer that I have not joined to
    the domain, (but which would be counted towards CALs etc).

    If so how? I'm prompted for the product key, have tried those I recieved
    with my SBS2003 package, but no luck.

    Thanks.
     
    PR, May 16, 2007
    #1
    1. Advertisements

  2. Yes you can use that, but I don't remember it ever asking for a key?
    I'm not a licensing Expert, but AFAIK those are for clients that connect to
    the SBS Server and are licensed to do so.

    The Outlook CD that came with your Server is a STAND alone Key
    And can be Installed using the Key on the back of the CD Case.
    (This is a Different Key than your SBS Key)

    As to why your Key is not working,
    Are you sure you have the KEY from the Outlook CD?

    Russ

    --

    Russell Grover
    SBITS.Biz
    Microsoft Certified Small Business Specialist.
    MCP, MCPS, MCNPS, (MCP-SBS)
    support @ SBITS.Biz
    Remote SBS2003 Support
    http://www.SBITS.Biz
     
    Russ Grover \(SBITS.Biz\), May 17, 2007
    #2
    1. Advertisements

  3. Hello Customer,

    Thank you for posting here.

    According to your description, I understand that you want to access SBS
    share folder to install Outlook 2003 for a computer which does not join in
    SBS domain. If I have misunderstood the problem, please don't hesitate to
    let me know.

    Based on my research, the Outlook installation file in the SBS share folder
    is integrated with SBS. You buy it together with the SBS. And the SBS only
    support the computer which joins in the domain to install the Outlook. If
    the computer does not join domain, the prompt to input product key is
    by-design. And this behave will break license.

    When the computer join domain, the computer name will apply in the Server
    Management console->Standard Management->Client Computers.

    If you want to install the Outlook 2003 on the computer which join domain,
    please use the Assign Applications Wizard, but not access the share folder
    on SBS.

    I suggest we perform the following steps to install Outlook 2003 on client
    computer, it will no need to input product key:

    1. On the computer, access http://SBSname/connectcomputer, finish the
    ConnectComputer wizard to join the computer in SBS domain.

    2. Open Management console->Standard Management->Client Computers, click
    Assign Applications to Client Computers link in right pane

    3. In the Assign Applications Wizard, click Next, select the computer join
    domain in step1, click Add, click Next,

    4. Tick Microsoft Office Outlook 2003, click next.

    5. Then finish the wizard,

    6. Restart the client computer, then, you will get prompt to install
    Outlook 2003.

    Hope these steps will give you some help.

    Thanks and have a nice day!

    Best regards,

    Terence Liu(MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    | From: "PR" <>
    | Subject: Use Outlook 2003 from SBS2003 \\servername\ClientApps\outlook2003
    | Date: Wed, 16 May 2007 15:12:39 -0700
    | Lines: 16
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | X-RFC2646: Format=Flowed; Original
    | Message-ID: <>
    | Newsgroups: microsoft.public.windows.server.sbs
    | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net 209.234.154.253
    | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
    | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:37295
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | Anyone,
    |
    | Having tried and failed, I ask:
    | Is it possible to install Outlook 2003 from the
    | (\\servername\ClientApps\outlook2003\setup.exe
    | Having tried and faiHaving tried and failed, I ask:
    | Can I use Outlook 2003 from SBS2003 on computer that I have not joined to
    | the domain, (but which would be counted towards CALs etc).
    |
    | If so how? I'm prompted for the product key, have tried those I recieved
    | with my SBS2003 package, but no luck.
    |
    | Thanks.
    |
    |
    |
    |
     
    Terence Liu [MSFT], May 17, 2007
    #3
  4. PR

    PR Guest

    Hello Terence,

    You almost - but not quite - got the gist of my problem/question:
    "Can I use Outlook 2003 from SBS2003 on computer that I have not joined to
    the domain?"

    a) I *don't* want to join this (and other similiar) computers to the domain.
    b) In this case the OS is non-supported for joining to domains anyway (XP
    Media Ed), and no, I cannot reinstall the OS for the work-around.
    c) These are private contractor's personal PC's which will come and go,
    usually only for a few months. But while they are here, we want to give them
    access to our Exchange server, using Outlook (not OE or other lightweight
    email client), because of scheduling (calendar) and tasks sharing/tracking.
    (Big reason why we purchased SBS2003).

    Given that I have a CD, one would assume (silly me) that I can install
    Outlook 'stand-alone' anytime I want that device to connect to our Exchange
    server.
    As long as I do not exceed my CALs limit, I would hope that this is
    OK|legal|possible. In reviewing the forum here, I found various posts that
    attempt to deal with the licensing issues - from what I've read, what I'm
    trying to do should be OK?

    Are you saying that I *must* join computers to the domain in order to comply
    with the licensing requirements of SBS2003?

    Thanks.
     
    PR, May 17, 2007
    #4
  5. If they're going to connect to your Exchange, then you definitely need
    enough CALs to cover them. But if the computers aren't in your control
    (owned by others), and will be 'coming and going' then I'd suggest they use
    OWA, or provide their own copy of Outlook and you can configure it to
    connect to your Exchange.

    The features you want should be available via OWA.

    Another idea, in situations like this a Terminal Server is really useful.
     
    Les Connor [SBS MVP], May 17, 2007
    #5
  6. Hello Customer,

    Thank you for kind update.

    We can not install Outlook 2003 from SBS 2003 share folder, if the client
    computer does not join SBS domain.

    The license of the intergraded Outlook 2003 depends on SBS 2003 client
    license. That why you only have SBS key and without Outlook 2003 separate
    key.

    When you prompt to input Outlook PK, you can try to input SBS 2003 PK. If
    it does not work, we can only say that the license has restricted here.

    For detail info about CAL of SBS, you can visit the following links:

    Licensing for Windows Small Business Server 2003 R2
    http://www.microsoft.com/windowsserver2003/sbs/howtobuy/licensing.mspx

    Windows Small Business Server 2003 R2: Frequently Asked Questions
    http://www.microsoft.com/WindowsServer2003/sbs/evaluation/faq/licensing.mspx

    You also can call our Licensing Office:

    You can call 1-800-426-9400 (select option 4), Monday through Friday, 6:00
    A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing
    specialist.

    Worldwide customers can use the Guide to Worldwide Microsoft Licensing
    Sites http://www.microsoft.com/licensing/index/worldwide.asp to find
    contact information in their locations.

    Meanwhile, Les's suggestion is very good. You can try to make the mobile
    client access your Exchange via OWA. The calendar and the Tasks can also
    work under OWA.

    If you have a separate Microsoft Office copy, you can also install Outlook
    from your Office disc. The stand-alone license Outlook can also connect
    Exchange server on SBS.

    Hope the info helps.

    Thank you and have a nice day.

    Best regards,

    Terence Liu(MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    | From: "PR" <>
    | References: <>
    <>
    | Subject: Re: Use Outlook 2003 from SBS2003
    \\servername\ClientApps\outlook2003
    | Date: Thu, 17 May 2007 09:42:19 -0700
    | Lines: 153
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | X-RFC2646: Format=Flowed; Original
    | Message-ID: <OnY#>
    | Newsgroups: microsoft.public.windows.server.sbs
    | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net 209.234.154.253
    | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:37464
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | Hello Terence,
    |
    | You almost - but not quite - got the gist of my problem/question:
    | "Can I use Outlook 2003 from SBS2003 on computer that I have not joined
    to
    | the domain?"
    |
    | a) I *don't* want to join this (and other similiar) computers to the
    domain.
    | b) In this case the OS is non-supported for joining to domains anyway (XP
    | Media Ed), and no, I cannot reinstall the OS for the work-around.
    | c) These are private contractor's personal PC's which will come and go,
    | usually only for a few months. But while they are here, we want to give
    them
    | access to our Exchange server, using Outlook (not OE or other lightweight
    | email client), because of scheduling (calendar) and tasks
    sharing/tracking.
    | (Big reason why we purchased SBS2003).
    |
    | Given that I have a CD, one would assume (silly me) that I can install
    | Outlook 'stand-alone' anytime I want that device to connect to our
    Exchange
    | server.
    | As long as I do not exceed my CALs limit, I would hope that this is
    | OK|legal|possible. In reviewing the forum here, I found various posts
    that
    | attempt to deal with the licensing issues - from what I've read, what I'm
    | trying to do should be OK?
    |
    | Are you saying that I *must* join computers to the domain in order to
    comply
    | with the licensing requirements of SBS2003?
    |
    | Thanks.
    |
    |
    | | > Hello Customer,
    | >
    | > Thank you for posting here.
    | >
    | > According to your description, I understand that you want to access SBS
    | > share folder to install Outlook 2003 for a computer which does not join
    in
    | > SBS domain. If I have misunderstood the problem, please don't hesitate
    to
    | > let me know.
    | >
    | > Based on my research, the Outlook installation file in the SBS share
    | > folder
    | > is integrated with SBS. You buy it together with the SBS. And the SBS
    only
    | > support the computer which joins in the domain to install the Outlook.
    If
    | > the computer does not join domain, the prompt to input product key is
    | > by-design. And this behave will break license.
    | >
    | > When the computer join domain, the computer name will apply in the
    Server
    | > Management console->Standard Management->Client Computers.
    | >
    | > If you want to install the Outlook 2003 on the computer which join
    domain,
    | > please use the Assign Applications Wizard, but not access the share
    folder
    | > on SBS.
    | >
    | > I suggest we perform the following steps to install Outlook 2003 on
    client
    | > computer, it will no need to input product key:
    | >
    | > 1. On the computer, access http://SBSname/connectcomputer, finish the
    | > ConnectComputer wizard to join the computer in SBS domain.
    | >
    | > 2. Open Management console->Standard Management->Client Computers, click
    | > Assign Applications to Client Computers link in right pane
    | >
    | > 3. In the Assign Applications Wizard, click Next, select the computer
    join
    | > domain in step1, click Add, click Next,
    | >
    | > 4. Tick Microsoft Office Outlook 2003, click next.
    | >
    | > 5. Then finish the wizard,
    | >
    | > 6. Restart the client computer, then, you will get prompt to install
    | > Outlook 2003.
    | >
    | > Hope these steps will give you some help.
    | >
    | > Thanks and have a nice day!
    | >
    | > Best regards,
    | >
    | > Terence Liu(MSFT)
    | >
    | > Microsoft CSS Online Newsgroup Support
    | >
    | > Get Secure! - www.microsoft.com/security
    | >
    | > =====================================================
    | > This newsgroup only focuses on SBS technical issues. If you have issues
    | > regarding other Microsoft products, you'd better post in the
    corresponding
    | > newsgroups so that they can be resolved in an efficient and timely
    manner.
    | > You can locate the newsgroup here:
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | >
    | > When opening a new thread via the web interface, we recommend you check
    | > the
    | > "Notify me of replies" box to receive e-mail notifications when there
    are
    | > any updates in your thread. When responding to posts via your
    newsreader,
    | > please "Reply to Group" so that others may learn and benefit from your
    | > issue.
    | >
    | > Microsoft engineers can only focus on one issue per thread. Although we
    | > provide other information for your reference, we recommend you post
    | > different incidents in different threads to keep the thread clean. In
    | > doing
    | > so, it will ensure your issues are resolved in a timely manner.
    | >
    | > For urgent issues, you may want to contact Microsoft CSS directly.
    Please
    | > check http://support.microsoft.com for regional support phone numbers.
    | >
    | > Any input or comments in this thread are highly appreciated.
    | > =====================================================
    | >
    | > This posting is provided "AS IS" with no warranties, and confers no
    | > rights.
    | >
    | > --------------------
    | > | From: "PR" <>
    | > | Subject: Use Outlook 2003 from SBS2003
    | > \\servername\ClientApps\outlook2003
    | > | Date: Wed, 16 May 2007 15:12:39 -0700
    | > | Lines: 16
    | > | X-Priority: 3
    | > | X-MSMail-Priority: Normal
    | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | X-RFC2646: Format=Flowed; Original
    | > | Message-ID: <>
    | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net
    209.234.154.253
    | > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
    | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:37295
    | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > |
    | > | Anyone,
    | > |
    | > | Having tried and failed, I ask:
    | > | Is it possible to install Outlook 2003 from the
    | > | (\\servername\ClientApps\outlook2003\setup.exe
    | > | Having tried and faiHaving tried and failed, I ask:
    | > | Can I use Outlook 2003 from SBS2003 on computer that I have not
    joined
    | > to
    | > | the domain, (but which would be counted towards CALs etc).
    | > |
    | > | If so how? I'm prompted for the product key, have tried those I
    recieved
    | > | with my SBS2003 package, but no luck.
    | > |
    | > | Thanks.
    | > |
    | > |
    | > |
    | > |
    | >
    |
    |
    |
     
    Terence Liu [MSFT], May 18, 2007
    #6
  7. Terrance I've never bought OEM Version of SBS
    But "EVERY" SBS Software I've installed has a Individual Key on the back of
    the Outlook 2003 CD
    Are you saying it's not supposed to be there?

    Russ

    --

    Russell Grover
    SBITS.Biz
    Microsoft Certified Small Business Specialist.
    MCP, MCPS, MCNPS, (MCP-SBS)
    support @ SBITS.Biz
    Remote SBS2003 Support
    http://www.SBITS.Biz
     
    Russ Grover \(SBITS.Biz\), May 18, 2007
    #7
  8. Hello Russ,

    Thank you for your reply.

    Yes, there is an Outlook 2003 key with SBS 2003. However, at mostly time,
    we do not use it. In the recommended installation steps, we do not need to
    input this key.

    You can find the key in the registry:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer

    Key: OutlookPID

    I'm not sure this key can work for this OEM issue. But as I know, this is
    not the recommended behave to use this key.

    I'm not a license engineer, for detail info about license, you can call our
    Licensing Office:

    You can call 1-800-426-9400 (select option 4), Monday through Friday, 6:00
    A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing
    specialist.

    Worldwide customers can use the Guide to Worldwide Microsoft Licensing
    Sites http://www.microsoft.com/licensing/index/worldwide.asp to find
    contact information in their locations.

    Thanks and have a nice day!

    Best regards,

    Terence Liu(MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    | From: "Russ Grover \(SBITS.Biz\)" <>
    | References: <>
    <>
    <OnY#>
    <NBLEe#>
    | Subject: Re: Use Outlook 2003 from SBS2003
    \\servername\ClientApps\outlook2003
    | Date: Thu, 17 May 2007 22:56:50 -0700
    | Lines: 313
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | X-RFC2646: Format=Flowed; Original
    | Message-ID: <>
    | Newsgroups: microsoft.public.windows.server.sbs
    | NNTP-Posting-Host: pool-71-182-82-124.ptldor.fios.verizon.net
    71.182.82.124
    | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
    | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:37656
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | Terrance I've never bought OEM Version of SBS
    | But "EVERY" SBS Software I've installed has a Individual Key on the back
    of
    | the Outlook 2003 CD
    | Are you saying it's not supposed to be there?
    |
    | Russ
    |
    | --
    |
    | Russell Grover
    | SBITS.Biz
    | Microsoft Certified Small Business Specialist.
    | MCP, MCPS, MCNPS, (MCP-SBS)
    | support @ SBITS.Biz
    | Remote SBS2003 Support
    | http://www.SBITS.Biz
    |
    |
    | | > Hello Customer,
    | >
    | > Thank you for kind update.
    | >
    | > We can not install Outlook 2003 from SBS 2003 share folder, if the
    client
    | > computer does not join SBS domain.
    | >
    | > The license of the intergraded Outlook 2003 depends on SBS 2003 client
    | > license. That why you only have SBS key and without Outlook 2003
    separate
    | > key.
    | >
    | > When you prompt to input Outlook PK, you can try to input SBS 2003 PK.
    If
    | > it does not work, we can only say that the license has restricted here.
    | >
    | > For detail info about CAL of SBS, you can visit the following links:
    | >
    | > Licensing for Windows Small Business Server 2003 R2
    | > http://www.microsoft.com/windowsserver2003/sbs/howtobuy/licensing.mspx
    | >
    | > Windows Small Business Server 2003 R2: Frequently Asked Questions
    | >
    http://www.microsoft.com/WindowsServer2003/sbs/evaluation/faq/licensing.mspx
    | >
    | > You also can call our Licensing Office:
    | >
    | > You can call 1-800-426-9400 (select option 4), Monday through Friday,
    6:00
    | > A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing
    | > specialist.
    | >
    | > Worldwide customers can use the Guide to Worldwide Microsoft Licensing
    | > Sites http://www.microsoft.com/licensing/index/worldwide.asp to find
    | > contact information in their locations.
    | >
    | > Meanwhile, Les's suggestion is very good. You can try to make the mobile
    | > client access your Exchange via OWA. The calendar and the Tasks can also
    | > work under OWA.
    | >
    | > If you have a separate Microsoft Office copy, you can also install
    Outlook
    | > from your Office disc. The stand-alone license Outlook can also connect
    | > Exchange server on SBS.
    | >
    | > Hope the info helps.
    | >
    | > Thank you and have a nice day.
    | >
    | > Best regards,
    | >
    | > Terence Liu(MSFT)
    | >
    | > Microsoft CSS Online Newsgroup Support
    | >
    | > Get Secure! - www.microsoft.com/security
    | >
    | > =====================================================
    | > This newsgroup only focuses on SBS technical issues. If you have issues
    | > regarding other Microsoft products, you'd better post in the
    corresponding
    | > newsgroups so that they can be resolved in an efficient and timely
    manner.
    | > You can locate the newsgroup here:
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | >
    | > When opening a new thread via the web interface, we recommend you check
    | > the
    | > "Notify me of replies" box to receive e-mail notifications when there
    are
    | > any updates in your thread. When responding to posts via your
    newsreader,
    | > please "Reply to Group" so that others may learn and benefit from your
    | > issue.
    | >
    | > Microsoft engineers can only focus on one issue per thread. Although we
    | > provide other information for your reference, we recommend you post
    | > different incidents in different threads to keep the thread clean. In
    | > doing
    | > so, it will ensure your issues are resolved in a timely manner.
    | >
    | > For urgent issues, you may want to contact Microsoft CSS directly.
    Please
    | > check http://support.microsoft.com for regional support phone numbers.
    | >
    | > Any input or comments in this thread are highly appreciated.
    | > =====================================================
    | >
    | > This posting is provided "AS IS" with no warranties, and confers no
    | > rights.
    | >
    | > --------------------
    | > | From: "PR" <>
    | > | References: <>
    | > <>
    | > | Subject: Re: Use Outlook 2003 from SBS2003
    | > \\servername\ClientApps\outlook2003
    | > | Date: Thu, 17 May 2007 09:42:19 -0700
    | > | Lines: 153
    | > | X-Priority: 3
    | > | X-MSMail-Priority: Normal
    | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | X-RFC2646: Format=Flowed; Original
    | > | Message-ID: <OnY#>
    | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net
    209.234.154.253
    | > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:37464
    | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > |
    | > | Hello Terence,
    | > |
    | > | You almost - but not quite - got the gist of my problem/question:
    | > | "Can I use Outlook 2003 from SBS2003 on computer that I have not
    joined
    | > to
    | > | the domain?"
    | > |
    | > | a) I *don't* want to join this (and other similiar) computers to the
    | > domain.
    | > | b) In this case the OS is non-supported for joining to domains anyway
    | > (XP
    | > | Media Ed), and no, I cannot reinstall the OS for the work-around.
    | > | c) These are private contractor's personal PC's which will come and
    go,
    | > | usually only for a few months. But while they are here, we want to
    give
    | > them
    | > | access to our Exchange server, using Outlook (not OE or other
    | > lightweight
    | > | email client), because of scheduling (calendar) and tasks
    | > sharing/tracking.
    | > | (Big reason why we purchased SBS2003).
    | > |
    | > | Given that I have a CD, one would assume (silly me) that I can install
    | > | Outlook 'stand-alone' anytime I want that device to connect to our
    | > Exchange
    | > | server.
    | > | As long as I do not exceed my CALs limit, I would hope that this is
    | > | OK|legal|possible. In reviewing the forum here, I found various posts
    | > that
    | > | attempt to deal with the licensing issues - from what I've read, what
    | > I'm
    | > | trying to do should be OK?
    | > |
    | > | Are you saying that I *must* join computers to the domain in order to
    | > comply
    | > | with the licensing requirements of SBS2003?
    | > |
    | > | Thanks.
    | > |
    | > |
    | > | | > | > Hello Customer,
    | > | >
    | > | > Thank you for posting here.
    | > | >
    | > | > According to your description, I understand that you want to access
    | > SBS
    | > | > share folder to install Outlook 2003 for a computer which does not
    | > join
    | > in
    | > | > SBS domain. If I have misunderstood the problem, please don't
    hesitate
    | > to
    | > | > let me know.
    | > | >
    | > | > Based on my research, the Outlook installation file in the SBS share
    | > | > folder
    | > | > is integrated with SBS. You buy it together with the SBS. And the
    SBS
    | > only
    | > | > support the computer which joins in the domain to install the
    Outlook.
    | > If
    | > | > the computer does not join domain, the prompt to input product key
    is
    | > | > by-design. And this behave will break license.
    | > | >
    | > | > When the computer join domain, the computer name will apply in the
    | > Server
    | > | > Management console->Standard Management->Client Computers.
    | > | >
    | > | > If you want to install the Outlook 2003 on the computer which join
    | > domain,
    | > | > please use the Assign Applications Wizard, but not access the share
    | > folder
    | > | > on SBS.
    | > | >
    | > | > I suggest we perform the following steps to install Outlook 2003 on
    | > client
    | > | > computer, it will no need to input product key:
    | > | >
    | > | > 1. On the computer, access http://SBSname/connectcomputer, finish
    the
    | > | > ConnectComputer wizard to join the computer in SBS domain.
    | > | >
    | > | > 2. Open Management console->Standard Management->Client Computers,
    | > click
    | > | > Assign Applications to Client Computers link in right pane
    | > | >
    | > | > 3. In the Assign Applications Wizard, click Next, select the
    computer
    | > join
    | > | > domain in step1, click Add, click Next,
    | > | >
    | > | > 4. Tick Microsoft Office Outlook 2003, click next.
    | > | >
    | > | > 5. Then finish the wizard,
    | > | >
    | > | > 6. Restart the client computer, then, you will get prompt to install
    | > | > Outlook 2003.
    | > | >
    | > | > Hope these steps will give you some help.
    | > | >
    | > | > Thanks and have a nice day!
    | > | >
    | > | > Best regards,
    | > | >
    | > | > Terence Liu(MSFT)
    | > | >
    | > | > Microsoft CSS Online Newsgroup Support
    | > | >
    | > | > Get Secure! - www.microsoft.com/security
    | > | >
    | > | > =====================================================
    | > | > This newsgroup only focuses on SBS technical issues. If you have
    | > issues
    | > | > regarding other Microsoft products, you'd better post in the
    | > corresponding
    | > | > newsgroups so that they can be resolved in an efficient and timely
    | > manner.
    | > | > You can locate the newsgroup here:
    | > | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | > | >
    | > | > When opening a new thread via the web interface, we recommend you
    | > check
    | > | > the
    | > | > "Notify me of replies" box to receive e-mail notifications when
    there
    | > are
    | > | > any updates in your thread. When responding to posts via your
    | > newsreader,
    | > | > please "Reply to Group" so that others may learn and benefit from
    your
    | > | > issue.
    | > | >
    | > | > Microsoft engineers can only focus on one issue per thread.
    Although
    | > we
    | > | > provide other information for your reference, we recommend you post
    | > | > different incidents in different threads to keep the thread clean.
    In
    | > | > doing
    | > | > so, it will ensure your issues are resolved in a timely manner.
    | > | >
    | > | > For urgent issues, you may want to contact Microsoft CSS directly.
    | > Please
    | > | > check http://support.microsoft.com for regional support phone
    numbers.
    | > | >
    | > | > Any input or comments in this thread are highly appreciated.
    | > | > =====================================================
    | > | >
    | > | > This posting is provided "AS IS" with no warranties, and confers no
    | > | > rights.
    | > | >
    | > | > --------------------
    | > | > | From: "PR" <>
    | > | > | Subject: Use Outlook 2003 from SBS2003
    | > | > \\servername\ClientApps\outlook2003
    | > | > | Date: Wed, 16 May 2007 15:12:39 -0700
    | > | > | Lines: 16
    | > | > | X-Priority: 3
    | > | > | X-MSMail-Priority: Normal
    | > | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | > | X-RFC2646: Format=Flowed; Original
    | > | > | Message-ID: <>
    | > | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | > | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net
    | > 209.234.154.253
    | > | > | Path:
    | > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
    | > | > | Xref: TK2MSFTNGHUB02.phx.gbl
    | > microsoft.public.windows.server.sbs:37295
    | > | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > | > |
    | > | > | Anyone,
    | > | > |
    | > | > | Having tried and failed, I ask:
    | > | > | Is it possible to install Outlook 2003 from the
    | > | > | (\\servername\ClientApps\outlook2003\setup.exe
    | > | > | Having tried and faiHaving tried and failed, I ask:
    | > | > | Can I use Outlook 2003 from SBS2003 on computer that I have not
    | > joined
    | > | > to
    | > | > | the domain, (but which would be counted towards CALs etc).
    | > | > |
    | > | > | If so how? I'm prompted for the product key, have tried those I
    | > recieved
    | > | > | with my SBS2003 package, but no luck.
    | > | > |
    | > | > | Thanks.
    | > | > |
    | > | > |
    | > | > |
    | > | > |
    | > | >
    | > |
    | > |
    | > |
    | >
    |
    |
    |
     
    Terence Liu [MSFT], May 18, 2007
    #8
  9. PR

    PR Guest

    Well well. Terence, yes you are not a license engineer, but your sure have
    implied (starting with your message on the 17th "And this behave will break
    license") knowledge that what I want to do would break the Microsoft
    Software License Terms. I'm glad I didn't stop there, since later that day,
    you then stated "When you prompt to input Outlook PK, you can try to input
    SBS 2003 PK. If it does not work, we can only say that the license has
    restricted here.", which is a more ambiguous answer - and clearly at odds
    with the first statement.
    Now today you state that there _is_ an Outlook key with SBS2003, talk about
    _recommended_ (which I stated from the first message was not my plan of
    action) installation steps, and even provide a registry location for the
    Key. (Which BTW my server install does have).

    So now finally I've located my copy of the "Microsoft Software License
    Terms" included in my OEM package, and it states (verbatim):
    2. USE RIGHTS.
    c. Running Instances of the Additional Software. You may run or otherwise
    use any number of instances of additional software listed below in physical
    or virtual operating system environments on any number of devices. You may
    use additional software only with the server software directly, or
    indirectly through additional software. As an exception, you may only use
    the SQL Management Tools, SQL Server 2005 Books Online and SQL Software
    Development Kit internally with the SQL Server portion of the software.
    * Server administration tools
    * Remote Desktop Connection
    * Office Outlook 2003
    * SQL...

    Unless my command of American legalese is really bad, it appears that what I
    want to accomplish is in fact authorized - that is, it won't break my
    software licensing terms - I just have to guess as to what the key for
    Outlook is. (Funny, why ship an Outlook CD, if the install from SBS2003
    already includes the client install?? Maybe someone predicted a use such as
    mine?)

    So can we quit guessing and get a definitive answer on this?
    Options:
    a) Yes the Office Outlook 2003 CD is intended for stand-alone installations,
    and a Product Key (PK) is provided as part of the SBS 2003 R2 Premuim
    Edition, (just that my OEM did/does not provide a (PK) in written format.)
    b) No, the Office Outlook 2003 CD is intended for back-up purposes, (and
    since I have no PK its actually quite useless in this instance, and
    therefore I should quit agonizing over this.)

    Thanks for taking the time - maybe someone else will learn from this.

    PR
     
    PR, May 18, 2007
    #9
  10. I've not read the entire thread but I've read enough to understand that what
    you want to do is install the copy of Outlook that was provided with your
    SBS software on to a computer that is not going to join the
    domain....missing any thing so far?

    1. There is no doubt that licensing is very confusing, but I can tell you
    that the MVPs have had this discussion numerous times with the SBS product
    group and the answer is ALWAYS the SAME: You can install as many instances
    of any client app that comes as a part of your SBS as you have CAL's.

    2. The reason you have the media is as a backup, in case of hardware
    failure and the need to re-install. OEM typically comes pre-installed.
    If you had ever installed on your own you would know that during the
    installation process you are prompted for the Outlook CD and ask for the
    PRODUCT KEY. Then you don't have to provide it during the install of
    domain clients because its build into the process.

    3. A CAL is required for any user/device that must provide an authenication
    to access resources on the server.

    SO, if your contractor's are accessing resources (files, email, etc) on the
    server, they require a CAL. And if you have a CAL for them, then you can
    install the Outlook software.

    If this doesn't work...as has been suggested, there's always OWA


    --
    Cris Hanna [SBS-MVP]
    -------------------------------------------------
    Microsoft MVPs
    Independent Experts (MVPs do not work for MS)
    Real World Answers
     
    Cris Hanna [SBS-MVP], May 18, 2007
    #10
  11. PR

    PR Guest

    Thanks for the input Chris.

    So working with the expectation that a standalone install of Outlook is
    within my licensing rights, now I'm back to my first question:
    The PK for Outlook as described above in Liu's message, (which in my case is
    the same as the SBS2003 server's), was not recognized by Outlook upon
    installation on a client PC, and I even tried:
    \\Sbs\ClientApps\outlook2003\setup.exe /L*V C:\install.txt PIDKEY=*PK* /qb
    according to varous Knowledge Base articles - the install appears to be
    fine, just wants a PK to run.

    Leaves me with: How do I accomplish this? What PK is the install asking for?

    And while I appreciate OWA (I'm using it now), it's not quite the same as
    using the heavy Outlook client - there are some differences - and since many
    (hurray MS) of these guys know and love Outlook, (unfortunately also many
    have AOL, Earthlink, gmail, OE etc.), we want a continued experience.
    Is this so unreasonable?


     
    PR, May 18, 2007
    #11
  12. So you have CAL's for machines that are not joining the domain?

    Its not really a question of what's reasonable or unreasonable...its more a
    question of what works and doesn't

    If you're OEM supplier failed to provide you a product key for the Outlook
    CD...its on them to give you one. Otherwise you're out of luck





    --
    Cris Hanna [SBS-MVP]
    -------------------------------------------------
    Microsoft MVPs
    Independent Experts (MVPs do not work for MS)
    Real World Answers
    ---------------------------------------------------------
    Please do not contact me directly regarding issues

     
    Cris Hanna [SBS-MVP], May 18, 2007
    #12
  13. Hello PR,

    Thank you for kind update. I'm sorry for the delay response due to the
    weekend.

    I'm sorry for my incorrect description about this Outlook license issue.

    Now, you have two PKs to have a try: the SBS PK and the Outlook PK in
    registry.

    For OEM SBS product, the SBS PK may work when you install the Outlook.

    For the publish SBS product, the Outlook key in the registry may Outlook.

    If the two keys do not fix your problem, you have to connect your OEM
    vendor to ask for the Outlook PK.

    Thanks for your understanding.

    Have a nice day.

    Best regards,

    Terence Liu(MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    | From: "PR" <>
    | References: <>
    <>
    <OnY#>
    <NBLEe#>
    <>
    <>
    | Subject: Re: Use Outlook 2003 from SBS2003
    \\servername\ClientApps\outlook2003
    | Date: Fri, 18 May 2007 10:27:33 -0700
    | Lines: 508
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | X-RFC2646: Format=Flowed; Original
    | Message-ID: <>
    | Newsgroups: microsoft.public.windows.server.sbs
    | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net 209.234.154.253
    | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:37800
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | Well well. Terence, yes you are not a license engineer, but your sure
    have
    | implied (starting with your message on the 17th "And this behave will
    break
    | license") knowledge that what I want to do would break the Microsoft
    | Software License Terms. I'm glad I didn't stop there, since later that
    day,
    | you then stated "When you prompt to input Outlook PK, you can try to
    input
    | SBS 2003 PK. If it does not work, we can only say that the license has
    | restricted here.", which is a more ambiguous answer - and clearly at odds
    | with the first statement.
    | Now today you state that there _is_ an Outlook key with SBS2003, talk
    about
    | _recommended_ (which I stated from the first message was not my plan of
    | action) installation steps, and even provide a registry location for the
    | Key. (Which BTW my server install does have).
    |
    | So now finally I've located my copy of the "Microsoft Software License
    | Terms" included in my OEM package, and it states (verbatim):
    | 2. USE RIGHTS.
    | c. Running Instances of the Additional Software. You may run or otherwise
    | use any number of instances of additional software listed below in
    physical
    | or virtual operating system environments on any number of devices. You
    may
    | use additional software only with the server software directly, or
    | indirectly through additional software. As an exception, you may only use
    | the SQL Management Tools, SQL Server 2005 Books Online and SQL Software
    | Development Kit internally with the SQL Server portion of the software.
    | * Server administration tools
    | * Remote Desktop Connection
    | * Office Outlook 2003
    | * SQL...
    |
    | Unless my command of American legalese is really bad, it appears that
    what I
    | want to accomplish is in fact authorized - that is, it won't break my
    | software licensing terms - I just have to guess as to what the key for
    | Outlook is. (Funny, why ship an Outlook CD, if the install from SBS2003
    | already includes the client install?? Maybe someone predicted a use such
    as
    | mine?)
    |
    | So can we quit guessing and get a definitive answer on this?
    | Options:
    | a) Yes the Office Outlook 2003 CD is intended for stand-alone
    installations,
    | and a Product Key (PK) is provided as part of the SBS 2003 R2 Premuim
    | Edition, (just that my OEM did/does not provide a (PK) in written format.)
    | b) No, the Office Outlook 2003 CD is intended for back-up purposes, (and
    | since I have no PK its actually quite useless in this instance, and
    | therefore I should quit agonizing over this.)
    |
    | Thanks for taking the time - maybe someone else will learn from this.
    |
    | PR
    |
    |
    | | > Hello Russ,
    | >
    | > Thank you for your reply.
    | >
    | > Yes, there is an Outlook 2003 key with SBS 2003. However, at mostly
    time,
    | > we do not use it. In the recommended installation steps, we do not need
    to
    | > input this key.
    | >
    | > You can find the key in the registry:
    | >
    | > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer
    | >
    | > Key: OutlookPID
    | >
    | > I'm not sure this key can work for this OEM issue. But as I know, this
    is
    | > not the recommended behave to use this key.
    | >
    | > I'm not a license engineer, for detail info about license, you can call
    | > our
    | > Licensing Office:
    | >
    | > You can call 1-800-426-9400 (select option 4), Monday through Friday,
    6:00
    | > A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing
    | > specialist.
    | >
    | > Worldwide customers can use the Guide to Worldwide Microsoft Licensing
    | > Sites http://www.microsoft.com/licensing/index/worldwide.asp to find
    | > contact information in their locations.
    | >
    | > Thanks and have a nice day!
    | >
    | > Best regards,
    | >
    | > Terence Liu(MSFT)
    | >
    | > Microsoft CSS Online Newsgroup Support
    | >
    | > Get Secure! - www.microsoft.com/security
    | >
    | > =====================================================
    | > This newsgroup only focuses on SBS technical issues. If you have issues
    | > regarding other Microsoft products, you'd better post in the
    corresponding
    | > newsgroups so that they can be resolved in an efficient and timely
    manner.
    | > You can locate the newsgroup here:
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | >
    | > When opening a new thread via the web interface, we recommend you check
    | > the
    | > "Notify me of replies" box to receive e-mail notifications when there
    are
    | > any updates in your thread. When responding to posts via your
    newsreader,
    | > please "Reply to Group" so that others may learn and benefit from your
    | > issue.
    | >
    | > Microsoft engineers can only focus on one issue per thread. Although we
    | > provide other information for your reference, we recommend you post
    | > different incidents in different threads to keep the thread clean. In
    | > doing
    | > so, it will ensure your issues are resolved in a timely manner.
    | >
    | > For urgent issues, you may want to contact Microsoft CSS directly.
    Please
    | > check http://support.microsoft.com for regional support phone numbers.
    | >
    | > Any input or comments in this thread are highly appreciated.
    | > =====================================================
    | >
    | > This posting is provided "AS IS" with no warranties, and confers no
    | > rights.
    | >
    | > --------------------
    | > | From: "Russ Grover \(SBITS.Biz\)" <>
    | > | References: <>
    | > <>
    | > <OnY#>
    | > <NBLEe#>
    | > | Subject: Re: Use Outlook 2003 from SBS2003
    | > \\servername\ClientApps\outlook2003
    | > | Date: Thu, 17 May 2007 22:56:50 -0700
    | > | Lines: 313
    | > | X-Priority: 3
    | > | X-MSMail-Priority: Normal
    | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | X-RFC2646: Format=Flowed; Original
    | > | Message-ID: <>
    | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | NNTP-Posting-Host: pool-71-182-82-124.ptldor.fios.verizon.net
    | > 71.182.82.124
    | > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
    | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:37656
    | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > |
    | > | Terrance I've never bought OEM Version of SBS
    | > | But "EVERY" SBS Software I've installed has a Individual Key on the
    back
    | > of
    | > | the Outlook 2003 CD
    | > | Are you saying it's not supposed to be there?
    | > |
    | > | Russ
    | > |
    | > | --
    | > |
    | > | Russell Grover
    | > | SBITS.Biz
    | > | Microsoft Certified Small Business Specialist.
    | > | MCP, MCPS, MCNPS, (MCP-SBS)
    | > | support @ SBITS.Biz
    | > | Remote SBS2003 Support
    | > | http://www.SBITS.Biz
    | > |
    | > |
    | > | | > | > Hello Customer,
    | > | >
    | > | > Thank you for kind update.
    | > | >
    | > | > We can not install Outlook 2003 from SBS 2003 share folder, if the
    | > client
    | > | > computer does not join SBS domain.
    | > | >
    | > | > The license of the intergraded Outlook 2003 depends on SBS 2003
    client
    | > | > license. That why you only have SBS key and without Outlook 2003
    | > separate
    | > | > key.
    | > | >
    | > | > When you prompt to input Outlook PK, you can try to input SBS 2003
    PK.
    | > If
    | > | > it does not work, we can only say that the license has restricted
    | > here.
    | > | >
    | > | > For detail info about CAL of SBS, you can visit the following links:
    | > | >
    | > | > Licensing for Windows Small Business Server 2003 R2
    | > | >
    http://www.microsoft.com/windowsserver2003/sbs/howtobuy/licensing.mspx
    | > | >
    | > | > Windows Small Business Server 2003 R2: Frequently Asked Questions
    | > | >
    | >
    http://www.microsoft.com/WindowsServer2003/sbs/evaluation/faq/licensing.mspx
    | > | >
    | > | > You also can call our Licensing Office:
    | > | >
    | > | > You can call 1-800-426-9400 (select option 4), Monday through
    Friday,
    | > 6:00
    | > | > A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing
    | > | > specialist.
    | > | >
    | > | > Worldwide customers can use the Guide to Worldwide Microsoft
    Licensing
    | > | > Sites http://www.microsoft.com/licensing/index/worldwide.asp to find
    | > | > contact information in their locations.
    | > | >
    | > | > Meanwhile, Les's suggestion is very good. You can try to make the
    | > mobile
    | > | > client access your Exchange via OWA. The calendar and the Tasks can
    | > also
    | > | > work under OWA.
    | > | >
    | > | > If you have a separate Microsoft Office copy, you can also install
    | > Outlook
    | > | > from your Office disc. The stand-alone license Outlook can also
    | > connect
    | > | > Exchange server on SBS.
    | > | >
    | > | > Hope the info helps.
    | > | >
    | > | > Thank you and have a nice day.
    | > | >
    | > | > Best regards,
    | > | >
    | > | > Terence Liu(MSFT)
    | > | >
    | > | > Microsoft CSS Online Newsgroup Support
    | > | >
    | > | > Get Secure! - www.microsoft.com/security
    | > | >
    | > | > =====================================================
    | > | > This newsgroup only focuses on SBS technical issues. If you have
    | > issues
    | > | > regarding other Microsoft products, you'd better post in the
    | > corresponding
    | > | > newsgroups so that they can be resolved in an efficient and timely
    | > manner.
    | > | > You can locate the newsgroup here:
    | > | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | > | >
    | > | > When opening a new thread via the web interface, we recommend you
    | > check
    | > | > the
    | > | > "Notify me of replies" box to receive e-mail notifications when
    there
    | > are
    | > | > any updates in your thread. When responding to posts via your
    | > newsreader,
    | > | > please "Reply to Group" so that others may learn and benefit from
    your
    | > | > issue.
    | > | >
    | > | > Microsoft engineers can only focus on one issue per thread.
    Although
    | > we
    | > | > provide other information for your reference, we recommend you post
    | > | > different incidents in different threads to keep the thread clean.
    In
    | > | > doing
    | > | > so, it will ensure your issues are resolved in a timely manner.
    | > | >
    | > | > For urgent issues, you may want to contact Microsoft CSS directly.
    | > Please
    | > | > check http://support.microsoft.com for regional support phone
    numbers.
    | > | >
    | > | > Any input or comments in this thread are highly appreciated.
    | > | > =====================================================
    | > | >
    | > | > This posting is provided "AS IS" with no warranties, and confers no
    | > | > rights.
    | > | >
    | > | > --------------------
    | > | > | From: "PR" <>
    | > | > | References: <>
    | > | > <>
    | > | > | Subject: Re: Use Outlook 2003 from SBS2003
    | > | > \\servername\ClientApps\outlook2003
    | > | > | Date: Thu, 17 May 2007 09:42:19 -0700
    | > | > | Lines: 153
    | > | > | X-Priority: 3
    | > | > | X-MSMail-Priority: Normal
    | > | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | > | X-RFC2646: Format=Flowed; Original
    | > | > | Message-ID: <OnY#>
    | > | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | > | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net
    | > 209.234.154.253
    | > | > | Path:
    | > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    | > | > | Xref: TK2MSFTNGHUB02.phx.gbl
    | > microsoft.public.windows.server.sbs:37464
    | > | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > | > |
    | > | > | Hello Terence,
    | > | > |
    | > | > | You almost - but not quite - got the gist of my problem/question:
    | > | > | "Can I use Outlook 2003 from SBS2003 on computer that I have not
    | > joined
    | > | > to
    | > | > | the domain?"
    | > | > |
    | > | > | a) I *don't* want to join this (and other similiar) computers to
    the
    | > | > domain.
    | > | > | b) In this case the OS is non-supported for joining to domains
    | > anyway
    | > | > (XP
    | > | > | Media Ed), and no, I cannot reinstall the OS for the work-around.
    | > | > | c) These are private contractor's personal PC's which will come
    and
    | > go,
    | > | > | usually only for a few months. But while they are here, we want to
    | > give
    | > | > them
    | > | > | access to our Exchange server, using Outlook (not OE or other
    | > | > lightweight
    | > | > | email client), because of scheduling (calendar) and tasks
    | > | > sharing/tracking.
    | > | > | (Big reason why we purchased SBS2003).
    | > | > |
    | > | > | Given that I have a CD, one would assume (silly me) that I can
    | > install
    | > | > | Outlook 'stand-alone' anytime I want that device to connect to our
    | > | > Exchange
    | > | > | server.
    | > | > | As long as I do not exceed my CALs limit, I would hope that this
    is
    | > | > | OK|legal|possible. In reviewing the forum here, I found various
    | > posts
    | > | > that
    | > | > | attempt to deal with the licensing issues - from what I've read,
    | > what
    | > | > I'm
    | > | > | trying to do should be OK?
    | > | > |
    | > | > | Are you saying that I *must* join computers to the domain in
    order
    | > to
    | > | > comply
    | > | > | with the licensing requirements of SBS2003?
    | > | > |
    | > | > | Thanks.
    | > | > |
    | > | > |
    | > message
    | > | > | | > | > | > Hello Customer,
    | > | > | >
    | > | > | > Thank you for posting here.
    | > | > | >
    | > | > | > According to your description, I understand that you want to
    | > access
    | > | > SBS
    | > | > | > share folder to install Outlook 2003 for a computer which does
    not
    | > | > join
    | > | > in
    | > | > | > SBS domain. If I have misunderstood the problem, please don't
    | > hesitate
    | > | > to
    | > | > | > let me know.
    | > | > | >
    | > | > | > Based on my research, the Outlook installation file in the SBS
    | > share
    | > | > | > folder
    | > | > | > is integrated with SBS. You buy it together with the SBS. And
    the
    | > SBS
    | > | > only
    | > | > | > support the computer which joins in the domain to install the
    | > Outlook.
    | > | > If
    | > | > | > the computer does not join domain, the prompt to input product
    key
    | > is
    | > | > | > by-design. And this behave will break license.
    | > | > | >
    | > | > | > When the computer join domain, the computer name will apply in
    the
    | > | > Server
    | > | > | > Management console->Standard Management->Client Computers.
    | > | > | >
    | > | > | > If you want to install the Outlook 2003 on the computer which
    join
    | > | > domain,
    | > | > | > please use the Assign Applications Wizard, but not access the
    | > share
    | > | > folder
    | > | > | > on SBS.
    | > | > | >
    | > | > | > I suggest we perform the following steps to install Outlook
    2003
    | > on
    | > | > client
    | > | > | > computer, it will no need to input product key:
    | > | > | >
    | > | > | > 1. On the computer, access http://SBSname/connectcomputer,
    finish
    | > the
    | > | > | > ConnectComputer wizard to join the computer in SBS domain.
    | > | > | >
    | > | > | > 2. Open Management console->Standard Management->Client
    Computers,
    | > | > click
    | > | > | > Assign Applications to Client Computers link in right pane
    | > | > | >
    | > | > | > 3. In the Assign Applications Wizard, click Next, select the
    | > computer
    | > | > join
    | > | > | > domain in step1, click Add, click Next,
    | > | > | >
    | > | > | > 4. Tick Microsoft Office Outlook 2003, click next.
    | > | > | >
    | > | > | > 5. Then finish the wizard,
    | > | > | >
    | > | > | > 6. Restart the client computer, then, you will get prompt to
    | > install
    | > | > | > Outlook 2003.
    | > | > | >
    | > | > | > Hope these steps will give you some help.
    | > | > | >
    | > | > | > Thanks and have a nice day!
    | > | > | >
    | > | > | > Best regards,
    | > | > | >
    | > | > | > Terence Liu(MSFT)
    | > | > | >
    | > | > | > Microsoft CSS Online Newsgroup Support
    | > | > | >
    | > | > | > Get Secure! - www.microsoft.com/security
    | > | > | >
    | > | > | > =====================================================
    | > | > | > This newsgroup only focuses on SBS technical issues. If you have
    | > | > issues
    | > | > | > regarding other Microsoft products, you'd better post in the
    | > | > corresponding
    | > | > | > newsgroups so that they can be resolved in an efficient and
    timely
    | > | > manner.
    | > | > | > You can locate the newsgroup here:
    | > | > | >
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | > | > | >
    | > | > | > When opening a new thread via the web interface, we recommend
    you
    | > | > check
    | > | > | > the
    | > | > | > "Notify me of replies" box to receive e-mail notifications when
    | > there
    | > | > are
    | > | > | > any updates in your thread. When responding to posts via your
    | > | > newsreader,
    | > | > | > please "Reply to Group" so that others may learn and benefit
    from
    | > your
    | > | > | > issue.
    | > | > | >
    | > | > | > Microsoft engineers can only focus on one issue per thread.
    | > Although
    | > | > we
    | > | > | > provide other information for your reference, we recommend you
    | > post
    | > | > | > different incidents in different threads to keep the thread
    clean.
    | > In
    | > | > | > doing
    | > | > | > so, it will ensure your issues are resolved in a timely manner.
    | > | > | >
    | > | > | > For urgent issues, you may want to contact Microsoft CSS
    directly.
    | > | > Please
    | > | > | > check http://support.microsoft.com for regional support phone
    | > numbers.
    | > | > | >
    | > | > | > Any input or comments in this thread are highly appreciated.
    | > | > | > =====================================================
    | > | > | >
    | > | > | > This posting is provided "AS IS" with no warranties, and
    confers
    | > no
    | > | > | > rights.
    | > | > | >
    | > | > | > --------------------
    | > | > | > | From: "PR" <>
    | > | > | > | Subject: Use Outlook 2003 from SBS2003
    | > | > | > \\servername\ClientApps\outlook2003
    | > | > | > | Date: Wed, 16 May 2007 15:12:39 -0700
    | > | > | > | Lines: 16
    | > | > | > | X-Priority: 3
    | > | > | > | X-MSMail-Priority: Normal
    | > | > | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | > | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | > | > | X-RFC2646: Format=Flowed; Original
    | > | > | > | Message-ID: <>
    | > | > | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | > | > | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net
    | > | > 209.234.154.253
    | > | > | > | Path:
    | > | > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
    | > | > | > | Xref: TK2MSFTNGHUB02.phx.gbl
    | > | > microsoft.public.windows.server.sbs:37295
    | > | > | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > | > | > |
    | > | > | > | Anyone,
    | > | > | > |
    | > | > | > | Having tried and failed, I ask:
    | > | > | > | Is it possible to install Outlook 2003 from the
    | > | > | > | (\\servername\ClientApps\outlook2003\setup.exe
    | > | > | > | Having tried and faiHaving tried and failed, I ask:
    | > | > | > | Can I use Outlook 2003 from SBS2003 on computer that I have
    not
    | > | > joined
    | > | > | > to
    | > | > | > | the domain, (but which would be counted towards CALs etc).
    | > | > | > |
    | > | > | > | If so how? I'm prompted for the product key, have tried those
    I
    | > | > recieved
    | > | > | > | with my SBS2003 package, but no luck.
    | > | > | > |
    | > | > | > | Thanks.
    | > | > | > |
    | > | > | > |
    | > | > | > |
    | > | > | > |
    | > | > | >
    | > | > |
    | > | > |
    | > | > |
    | > | >
    | > |
    | > |
    | > |
    | >
    |
    |
    |
     
    Terence Liu [MSFT], May 21, 2007
    #13
  14. PR

    PR Guest

    I love it! Need I say more?


    From: US_CAG_Customer_Care [mailto:]
    Sent: Sat 19-May-07 05:44
    To: PR
    Subject: Re: Customer Resolution Form Submission MISSING ITEM
    (KMM48183015I57L0KM)


    Dear PR,

    Thank you for contacting Dell Customer Care.

    I apologize for the delay in response to your e-mail. We currently have a
    backlog of e-mails and are working hard to answer all of them in a timely
    manner.

    I understand that you need the product key for your Outlook 2003 Standard. I
    appreciate the opportunity to assist you with this issue.

    I show that the Microsoft Product Key Info department will be able to best
    address your concern. Please call them directly at (800) 936-5700.

    I apologize that I am unable to assist you directly as Customer Care does
    not have the access to address your request. Thank you for your patience and
    understanding, both of which are greatly appreciated.

    Your case number for this interaction is xxxxx.

    For new issues, please use the following link to chat or e-mail with our
    E-Support teams.
    http://support.dell.com/support/top...are/en/contactus?c=us&cs=19&l=en&s=dhs&~ck=mn

    If there is anything additional that you need, please feel free to visit our
    online Customer Care Center at:

    http://www.support.dell.com or call us at 1800-624-9897 ext. 7266966.

    Again, thank you for choosing Dell Customer Care.

    Respectfully,

    Jane Madriaga
    Rep ID 0124888
    5:00 A.M. to 2:00 P.M. CST
    Dell Online Customer Care
     
    PR, May 21, 2007
    #14
  15. PR

    PR Guest

    Yes I have the CALs - in fact, purchased for this purpose - to connect
    additional users/devices.
    OEM responded today (see email after Liu's admission? that I'm within my
    licensing rights).
    OEM says its Microsoft's responsibility, Microsoft says its OEM's
    responsibility - classic.

    And based on Liu' message, my PK for Outlook as stored in the SBS registry
    (and again, same PK as my server software) might work - only it doesn't.

    As far as works/doesn't work, can I really be the first to need to do this?
    And if it doesn't work, then maybe there is a problem in the
    system/licensing/setup (?) that should be addressed - so until I know for a
    fact that this system was not designed to do this, (which would be contrary
    to the licensing terms), I'll continue to hope for a resolution.


     
    PR, May 21, 2007
    #15
  16. Hello PR,

    Thank you for kind posting back.

    Since the Dell told you how to resolve this issue, I suggest you to follow
    they explain and call our licensing office.

    Note: We do not support install the SBS bind Outlook on the client which do
    not join SBS domain. If you really want to do that, you have to resolve the
    problem you meet by yourself.

    If you have any concern about license of SBS, please call our licensing
    office:

    You can call 1-800-426-9400 (select option 4), Monday through Friday, 6:00
    A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing
    specialist.

    Worldwide customers can use the Guide to Worldwide Microsoft Licensing
    Sites http://www.microsoft.com/licensing/index/worldwide.asp to find
    contact information in their locations.

    Thanks and have a nice day!

    Best regards,

    Terence Liu(MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.
    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    | From: "PR" <>
    | References: <>
    <>
    <OnY#>
    <NBLEe#>
    <>
    <>
    <>
    <bHC$>
    | Subject: Re: Use Outlook 2003 from SBS2003
    \\servername\ClientApps\outlook2003
    | Date: Mon, 21 May 2007 10:58:51 -0700
    | Lines: 722
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | X-RFC2646: Format=Flowed; Original
    | Message-ID: <>
    | Newsgroups: microsoft.public.windows.server.sbs
    | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net 209.234.154.253
    | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:38324
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | I love it! Need I say more?
    |
    |
    | From: US_CAG_Customer_Care [mailto:]
    | Sent: Sat 19-May-07 05:44
    | To: PR
    | Subject: Re: Customer Resolution Form Submission MISSING ITEM
    | (KMM48183015I57L0KM)
    |
    |
    | Dear PR,
    |
    | Thank you for contacting Dell Customer Care.
    |
    | I apologize for the delay in response to your e-mail. We currently have a
    | backlog of e-mails and are working hard to answer all of them in a timely
    | manner.
    |
    | I understand that you need the product key for your Outlook 2003
    Standard. I
    | appreciate the opportunity to assist you with this issue.
    |
    | I show that the Microsoft Product Key Info department will be able to
    best
    | address your concern. Please call them directly at (800) 936-5700.
    |
    | I apologize that I am unable to assist you directly as Customer Care does
    | not have the access to address your request. Thank you for your patience
    and
    | understanding, both of which are greatly appreciated.
    |
    | Your case number for this interaction is xxxxx.
    |
    | For new issues, please use the following link to chat or e-mail with our
    | E-Support teams.
    |
    http://support.dell.com/support/topics/global.aspx/support/dellcare/en/conta
    ctus?c=us&cs=19&l=en&s=dhs&~ck=mn
    |
    | If there is anything additional that you need, please feel free to visit
    our
    | online Customer Care Center at:
    |
    | http://www.support.dell.com or call us at 1800-624-9897 ext. 7266966.
    |
    | Again, thank you for choosing Dell Customer Care.
    |
    | Respectfully,
    |
    | Jane Madriaga
    | Rep ID 0124888
    | 5:00 A.M. to 2:00 P.M. CST
    | Dell Online Customer Care
    |
    |
    | | > Hello PR,
    | >
    | > Thank you for kind update. I'm sorry for the delay response due to the
    | > weekend.
    | >
    | > I'm sorry for my incorrect description about this Outlook license issue.
    | >
    | > Now, you have two PKs to have a try: the SBS PK and the Outlook PK in
    | > registry.
    | >
    | > For OEM SBS product, the SBS PK may work when you install the Outlook.
    | >
    | > For the publish SBS product, the Outlook key in the registry may
    Outlook.
    | >
    | > If the two keys do not fix your problem, you have to connect your OEM
    | > vendor to ask for the Outlook PK.
    | >
    | > Thanks for your understanding.
    | >
    | > Have a nice day.
    | >
    | > Best regards,
    | >
    | > Terence Liu(MSFT)
    | >
    | > Microsoft CSS Online Newsgroup Support
    | >
    | > Get Secure! - www.microsoft.com/security
    | >
    | > =====================================================
    | > This newsgroup only focuses on SBS technical issues. If you have issues
    | > regarding other Microsoft products, you'd better post in the
    corresponding
    | > newsgroups so that they can be resolved in an efficient and timely
    manner.
    | > You can locate the newsgroup here:
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | >
    | > When opening a new thread via the web interface, we recommend you check
    | > the
    | > "Notify me of replies" box to receive e-mail notifications when there
    are
    | > any updates in your thread. When responding to posts via your
    newsreader,
    | > please "Reply to Group" so that others may learn and benefit from your
    | > issue.
    | >
    | > Microsoft engineers can only focus on one issue per thread. Although we
    | > provide other information for your reference, we recommend you post
    | > different incidents in different threads to keep the thread clean. In
    | > doing
    | > so, it will ensure your issues are resolved in a timely manner.
    | >
    | > For urgent issues, you may want to contact Microsoft CSS directly.
    Please
    | > check http://support.microsoft.com for regional support phone numbers.
    | >
    | > Any input or comments in this thread are highly appreciated.
    | > =====================================================
    | >
    | > This posting is provided "AS IS" with no warranties, and confers no
    | > rights.
    | >
    | > --------------------
    | > | From: "PR" <>
    | > | References: <>
    | > <>
    | > <OnY#>
    | > <NBLEe#>
    | > <>
    | > <>
    | > | Subject: Re: Use Outlook 2003 from SBS2003
    | > \\servername\ClientApps\outlook2003
    | > | Date: Fri, 18 May 2007 10:27:33 -0700
    | > | Lines: 508
    | > | X-Priority: 3
    | > | X-MSMail-Priority: Normal
    | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | X-RFC2646: Format=Flowed; Original
    | > | Message-ID: <>
    | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net
    209.234.154.253
    | > | Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    | > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:37800
    | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > |
    | > | Well well. Terence, yes you are not a license engineer, but your sure
    | > have
    | > | implied (starting with your message on the 17th "And this behave will
    | > break
    | > | license") knowledge that what I want to do would break the Microsoft
    | > | Software License Terms. I'm glad I didn't stop there, since later that
    | > day,
    | > | you then stated "When you prompt to input Outlook PK, you can try to
    | > input
    | > | SBS 2003 PK. If it does not work, we can only say that the license has
    | > | restricted here.", which is a more ambiguous answer - and clearly at
    | > odds
    | > | with the first statement.
    | > | Now today you state that there _is_ an Outlook key with SBS2003, talk
    | > about
    | > | _recommended_ (which I stated from the first message was not my plan
    of
    | > | action) installation steps, and even provide a registry location for
    the
    | > | Key. (Which BTW my server install does have).
    | > |
    | > | So now finally I've located my copy of the "Microsoft Software License
    | > | Terms" included in my OEM package, and it states (verbatim):
    | > | 2. USE RIGHTS.
    | > | c. Running Instances of the Additional Software. You may run or
    | > otherwise
    | > | use any number of instances of additional software listed below in
    | > physical
    | > | or virtual operating system environments on any number of devices. You
    | > may
    | > | use additional software only with the server software directly, or
    | > | indirectly through additional software. As an exception, you may only
    | > use
    | > | the SQL Management Tools, SQL Server 2005 Books Online and SQL
    Software
    | > | Development Kit internally with the SQL Server portion of the
    software.
    | > | * Server administration tools
    | > | * Remote Desktop Connection
    | > | * Office Outlook 2003
    | > | * SQL...
    | > |
    | > | Unless my command of American legalese is really bad, it appears that
    | > what I
    | > | want to accomplish is in fact authorized - that is, it won't break my
    | > | software licensing terms - I just have to guess as to what the key for
    | > | Outlook is. (Funny, why ship an Outlook CD, if the install from
    SBS2003
    | > | already includes the client install?? Maybe someone predicted a use
    such
    | > as
    | > | mine?)
    | > |
    | > | So can we quit guessing and get a definitive answer on this?
    | > | Options:
    | > | a) Yes the Office Outlook 2003 CD is intended for stand-alone
    | > installations,
    | > | and a Product Key (PK) is provided as part of the SBS 2003 R2 Premuim
    | > | Edition, (just that my OEM did/does not provide a (PK) in written
    | > format.)
    | > | b) No, the Office Outlook 2003 CD is intended for back-up purposes,
    (and
    | > | since I have no PK its actually quite useless in this instance, and
    | > | therefore I should quit agonizing over this.)
    | > |
    | > | Thanks for taking the time - maybe someone else will learn from this.
    | > |
    | > | PR
    | > |
    | > |
    | > | | > | > Hello Russ,
    | > | >
    | > | > Thank you for your reply.
    | > | >
    | > | > Yes, there is an Outlook 2003 key with SBS 2003. However, at mostly
    | > time,
    | > | > we do not use it. In the recommended installation steps, we do not
    | > need
    | > to
    | > | > input this key.
    | > | >
    | > | > You can find the key in the registry:
    | > | >
    | > | > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer
    | > | >
    | > | > Key: OutlookPID
    | > | >
    | > | > I'm not sure this key can work for this OEM issue. But as I know,
    this
    | > is
    | > | > not the recommended behave to use this key.
    | > | >
    | > | > I'm not a license engineer, for detail info about license, you can
    | > call
    | > | > our
    | > | > Licensing Office:
    | > | >
    | > | > You can call 1-800-426-9400 (select option 4), Monday through
    Friday,
    | > 6:00
    | > | > A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft licensing
    | > | > specialist.
    | > | >
    | > | > Worldwide customers can use the Guide to Worldwide Microsoft
    Licensing
    | > | > Sites http://www.microsoft.com/licensing/index/worldwide.asp to find
    | > | > contact information in their locations.
    | > | >
    | > | > Thanks and have a nice day!
    | > | >
    | > | > Best regards,
    | > | >
    | > | > Terence Liu(MSFT)
    | > | >
    | > | > Microsoft CSS Online Newsgroup Support
    | > | >
    | > | > Get Secure! - www.microsoft.com/security
    | > | >
    | > | > =====================================================
    | > | > This newsgroup only focuses on SBS technical issues. If you have
    | > issues
    | > | > regarding other Microsoft products, you'd better post in the
    | > corresponding
    | > | > newsgroups so that they can be resolved in an efficient and timely
    | > manner.
    | > | > You can locate the newsgroup here:
    | > | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | > | >
    | > | > When opening a new thread via the web interface, we recommend you
    | > check
    | > | > the
    | > | > "Notify me of replies" box to receive e-mail notifications when
    there
    | > are
    | > | > any updates in your thread. When responding to posts via your
    | > newsreader,
    | > | > please "Reply to Group" so that others may learn and benefit from
    your
    | > | > issue.
    | > | >
    | > | > Microsoft engineers can only focus on one issue per thread.
    Although
    | > we
    | > | > provide other information for your reference, we recommend you post
    | > | > different incidents in different threads to keep the thread clean.
    In
    | > | > doing
    | > | > so, it will ensure your issues are resolved in a timely manner.
    | > | >
    | > | > For urgent issues, you may want to contact Microsoft CSS directly.
    | > Please
    | > | > check http://support.microsoft.com for regional support phone
    numbers.
    | > | >
    | > | > Any input or comments in this thread are highly appreciated.
    | > | > =====================================================
    | > | >
    | > | > This posting is provided "AS IS" with no warranties, and confers no
    | > | > rights.
    | > | >
    | > | > --------------------
    | > | > | From: "Russ Grover \(SBITS.Biz\)" <>
    | > | > | References: <>
    | > | > <>
    | > | > <OnY#>
    | > | > <NBLEe#>
    | > | > | Subject: Re: Use Outlook 2003 from SBS2003
    | > | > \\servername\ClientApps\outlook2003
    | > | > | Date: Thu, 17 May 2007 22:56:50 -0700
    | > | > | Lines: 313
    | > | > | X-Priority: 3
    | > | > | X-MSMail-Priority: Normal
    | > | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | > | X-RFC2646: Format=Flowed; Original
    | > | > | Message-ID: <>
    | > | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | > | NNTP-Posting-Host: pool-71-182-82-124.ptldor.fios.verizon.net
    | > | > 71.182.82.124
    | > | > | Path:
    | > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
    | > | > | Xref: TK2MSFTNGHUB02.phx.gbl
    | > microsoft.public.windows.server.sbs:37656
    | > | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > | > |
    | > | > | Terrance I've never bought OEM Version of SBS
    | > | > | But "EVERY" SBS Software I've installed has a Individual Key on
    the
    | > back
    | > | > of
    | > | > | the Outlook 2003 CD
    | > | > | Are you saying it's not supposed to be there?
    | > | > |
    | > | > | Russ
    | > | > |
    | > | > | --
    | > | > |
    | > | > | Russell Grover
    | > | > | SBITS.Biz
    | > | > | Microsoft Certified Small Business Specialist.
    | > | > | MCP, MCPS, MCNPS, (MCP-SBS)
    | > | > | support @ SBITS.Biz
    | > | > | Remote SBS2003 Support
    | > | > | http://www.SBITS.Biz
    | > | > |
    | > | > |
    | > message
    | > | > | | > | > | > Hello Customer,
    | > | > | >
    | > | > | > Thank you for kind update.
    | > | > | >
    | > | > | > We can not install Outlook 2003 from SBS 2003 share folder, if
    the
    | > | > client
    | > | > | > computer does not join SBS domain.
    | > | > | >
    | > | > | > The license of the intergraded Outlook 2003 depends on SBS 2003
    | > client
    | > | > | > license. That why you only have SBS key and without Outlook 2003
    | > | > separate
    | > | > | > key.
    | > | > | >
    | > | > | > When you prompt to input Outlook PK, you can try to input SBS
    2003
    | > PK.
    | > | > If
    | > | > | > it does not work, we can only say that the license has
    restricted
    | > | > here.
    | > | > | >
    | > | > | > For detail info about CAL of SBS, you can visit the following
    | > links:
    | > | > | >
    | > | > | > Licensing for Windows Small Business Server 2003 R2
    | > | > | >
    | > http://www.microsoft.com/windowsserver2003/sbs/howtobuy/licensing.mspx
    | > | > | >
    | > | > | > Windows Small Business Server 2003 R2: Frequently Asked
    Questions
    | > | > | >
    | > | >
    | >
    http://www.microsoft.com/WindowsServer2003/sbs/evaluation/faq/licensing.mspx
    | > | > | >
    | > | > | > You also can call our Licensing Office:
    | > | > | >
    | > | > | > You can call 1-800-426-9400 (select option 4), Monday through
    | > Friday,
    | > | > 6:00
    | > | > | > A.M. to 5:30 P.M. (PST) to speak directly to a Microsoft
    licensing
    | > | > | > specialist.
    | > | > | >
    | > | > | > Worldwide customers can use the Guide to Worldwide Microsoft
    | > Licensing
    | > | > | > Sites http://www.microsoft.com/licensing/index/worldwide.asp to
    | > find
    | > | > | > contact information in their locations.
    | > | > | >
    | > | > | > Meanwhile, Les's suggestion is very good. You can try to make
    the
    | > | > mobile
    | > | > | > client access your Exchange via OWA. The calendar and the Tasks
    | > can
    | > | > also
    | > | > | > work under OWA.
    | > | > | >
    | > | > | > If you have a separate Microsoft Office copy, you can also
    install
    | > | > Outlook
    | > | > | > from your Office disc. The stand-alone license Outlook can also
    | > | > connect
    | > | > | > Exchange server on SBS.
    | > | > | >
    | > | > | > Hope the info helps.
    | > | > | >
    | > | > | > Thank you and have a nice day.
    | > | > | >
    | > | > | > Best regards,
    | > | > | >
    | > | > | > Terence Liu(MSFT)
    | > | > | >
    | > | > | > Microsoft CSS Online Newsgroup Support
    | > | > | >
    | > | > | > Get Secure! - www.microsoft.com/security
    | > | > | >
    | > | > | > =====================================================
    | > | > | > This newsgroup only focuses on SBS technical issues. If you have
    | > | > issues
    | > | > | > regarding other Microsoft products, you'd better post in the
    | > | > corresponding
    | > | > | > newsgroups so that they can be resolved in an efficient and
    timely
    | > | > manner.
    | > | > | > You can locate the newsgroup here:
    | > | > | >
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | > | > | >
    | > | > | > When opening a new thread via the web interface, we recommend
    you
    | > | > check
    | > | > | > the
    | > | > | > "Notify me of replies" box to receive e-mail notifications when
    | > there
    | > | > are
    | > | > | > any updates in your thread. When responding to posts via your
    | > | > newsreader,
    | > | > | > please "Reply to Group" so that others may learn and benefit
    from
    | > your
    | > | > | > issue.
    | > | > | >
    | > | > | > Microsoft engineers can only focus on one issue per thread.
    | > Although
    | > | > we
    | > | > | > provide other information for your reference, we recommend you
    | > post
    | > | > | > different incidents in different threads to keep the thread
    clean.
    | > In
    | > | > | > doing
    | > | > | > so, it will ensure your issues are resolved in a timely manner.
    | > | > | >
    | > | > | > For urgent issues, you may want to contact Microsoft CSS
    directly.
    | > | > Please
    | > | > | > check http://support.microsoft.com for regional support phone
    | > numbers.
    | > | > | >
    | > | > | > Any input or comments in this thread are highly appreciated.
    | > | > | > =====================================================
    | > | > | >
    | > | > | > This posting is provided "AS IS" with no warranties, and
    confers
    | > no
    | > | > | > rights.
    | > | > | >
    | > | > | > --------------------
    | > | > | > | From: "PR" <>
    | > | > | > | References: <>
    | > | > | > <>
    | > | > | > | Subject: Re: Use Outlook 2003 from SBS2003
    | > | > | > \\servername\ClientApps\outlook2003
    | > | > | > | Date: Thu, 17 May 2007 09:42:19 -0700
    | > | > | > | Lines: 153
    | > | > | > | X-Priority: 3
    | > | > | > | X-MSMail-Priority: Normal
    | > | > | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | > | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | > | > | X-RFC2646: Format=Flowed; Original
    | > | > | > | Message-ID: <OnY#>
    | > | > | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | > | > | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net
    | > | > 209.234.154.253
    | > | > | > | Path:
    | > | > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
    | > | > | > | Xref: TK2MSFTNGHUB02.phx.gbl
    | > | > microsoft.public.windows.server.sbs:37464
    | > | > | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > | > | > |
    | > | > | > | Hello Terence,
    | > | > | > |
    | > | > | > | You almost - but not quite - got the gist of my
    | > problem/question:
    | > | > | > | "Can I use Outlook 2003 from SBS2003 on computer that I have
    not
    | > | > joined
    | > | > | > to
    | > | > | > | the domain?"
    | > | > | > |
    | > | > | > | a) I *don't* want to join this (and other similiar) computers
    to
    | > the
    | > | > | > domain.
    | > | > | > | b) In this case the OS is non-supported for joining to domains
    | > | > anyway
    | > | > | > (XP
    | > | > | > | Media Ed), and no, I cannot reinstall the OS for the
    | > work-around.
    | > | > | > | c) These are private contractor's personal PC's which will
    come
    | > and
    | > | > go,
    | > | > | > | usually only for a few months. But while they are here, we
    want
    | > to
    | > | > give
    | > | > | > them
    | > | > | > | access to our Exchange server, using Outlook (not OE or other
    | > | > | > lightweight
    | > | > | > | email client), because of scheduling (calendar) and tasks
    | > | > | > sharing/tracking.
    | > | > | > | (Big reason why we purchased SBS2003).
    | > | > | > |
    | > | > | > | Given that I have a CD, one would assume (silly me) that I can
    | > | > install
    | > | > | > | Outlook 'stand-alone' anytime I want that device to connect
    to
    | > our
    | > | > | > Exchange
    | > | > | > | server.
    | > | > | > | As long as I do not exceed my CALs limit, I would hope that
    this
    | > is
    | > | > | > | OK|legal|possible. In reviewing the forum here, I found
    various
    | > | > posts
    | > | > | > that
    | > | > | > | attempt to deal with the licensing issues - from what I've
    read,
    | > | > what
    | > | > | > I'm
    | > | > | > | trying to do should be OK?
    | > | > | > |
    | > | > | > | Are you saying that I *must* join computers to the domain in
    | > order
    | > | > to
    | > | > | > comply
    | > | > | > | with the licensing requirements of SBS2003?
    | > | > | > |
    | > | > | > | Thanks.
    | > | > | > |
    | > | > | > |
    | > | > message
    | > | > | > | | > | > | > | > Hello Customer,
    | > | > | > | >
    | > | > | > | > Thank you for posting here.
    | > | > | > | >
    | > | > | > | > According to your description, I understand that you want to
    | > | > access
    | > | > | > SBS
    | > | > | > | > share folder to install Outlook 2003 for a computer which
    does
    | > not
    | > | > | > join
    | > | > | > in
    | > | > | > | > SBS domain. If I have misunderstood the problem, please
    don't
    | > | > hesitate
    | > | > | > to
    | > | > | > | > let me know.
    | > | > | > | >
    | > | > | > | > Based on my research, the Outlook installation file in the
    SBS
    | > | > share
    | > | > | > | > folder
    | > | > | > | > is integrated with SBS. You buy it together with the SBS.
    And
    | > the
    | > | > SBS
    | > | > | > only
    | > | > | > | > support the computer which joins in the domain to install
    the
    | > | > Outlook.
    | > | > | > If
    | > | > | > | > the computer does not join domain, the prompt to input
    product
    | > key
    | > | > is
    | > | > | > | > by-design. And this behave will break license.
    | > | > | > | >
    | > | > | > | > When the computer join domain, the computer name will apply
    in
    | > the
    | > | > | > Server
    | > | > | > | > Management console->Standard Management->Client Computers.
    | > | > | > | >
    | > | > | > | > If you want to install the Outlook 2003 on the computer
    which
    | > join
    | > | > | > domain,
    | > | > | > | > please use the Assign Applications Wizard, but not access
    the
    | > | > share
    | > | > | > folder
    | > | > | > | > on SBS.
    | > | > | > | >
    | > | > | > | > I suggest we perform the following steps to install Outlook
    | > 2003
    | > | > on
    | > | > | > client
    | > | > | > | > computer, it will no need to input product key:
    | > | > | > | >
    | > | > | > | > 1. On the computer, access http://SBSname/connectcomputer,
    | > finish
    | > | > the
    | > | > | > | > ConnectComputer wizard to join the computer in SBS domain.
    | > | > | > | >
    | > | > | > | > 2. Open Management console->Standard Management->Client
    | > Computers,
    | > | > | > click
    | > | > | > | > Assign Applications to Client Computers link in right pane
    | > | > | > | >
    | > | > | > | > 3. In the Assign Applications Wizard, click Next, select the
    | > | > computer
    | > | > | > join
    | > | > | > | > domain in step1, click Add, click Next,
    | > | > | > | >
    | > | > | > | > 4. Tick Microsoft Office Outlook 2003, click next.
    | > | > | > | >
    | > | > | > | > 5. Then finish the wizard,
    | > | > | > | >
    | > | > | > | > 6. Restart the client computer, then, you will get prompt to
    | > | > install
    | > | > | > | > Outlook 2003.
    | > | > | > | >
    | > | > | > | > Hope these steps will give you some help.
    | > | > | > | >
    | > | > | > | > Thanks and have a nice day!
    | > | > | > | >
    | > | > | > | > Best regards,
    | > | > | > | >
    | > | > | > | > Terence Liu(MSFT)
    | > | > | > | >
    | > | > | > | > Microsoft CSS Online Newsgroup Support
    | > | > | > | >
    | > | > | > | > Get Secure! - www.microsoft.com/security
    | > | > | > | >
    | > | > | > | > =====================================================
    | > | > | > | > This newsgroup only focuses on SBS technical issues. If you
    | > have
    | > | > | > issues
    | > | > | > | > regarding other Microsoft products, you'd better post in the
    | > | > | > corresponding
    | > | > | > | > newsgroups so that they can be resolved in an efficient and
    | > timely
    | > | > | > manner.
    | > | > | > | > You can locate the newsgroup here:
    | > | > | > | >
    | > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
    | > | > | > | >
    | > | > | > | > When opening a new thread via the web interface, we
    recommend
    | > you
    | > | > | > check
    | > | > | > | > the
    | > | > | > | > "Notify me of replies" box to receive e-mail notifications
    | > when
    | > | > there
    | > | > | > are
    | > | > | > | > any updates in your thread. When responding to posts via
    your
    | > | > | > newsreader,
    | > | > | > | > please "Reply to Group" so that others may learn and benefit
    | > from
    | > | > your
    | > | > | > | > issue.
    | > | > | > | >
    | > | > | > | > Microsoft engineers can only focus on one issue per thread.
    | > | > Although
    | > | > | > we
    | > | > | > | > provide other information for your reference, we recommend
    you
    | > | > post
    | > | > | > | > different incidents in different threads to keep the thread
    | > clean.
    | > | > In
    | > | > | > | > doing
    | > | > | > | > so, it will ensure your issues are resolved in a timely
    | > manner.
    | > | > | > | >
    | > | > | > | > For urgent issues, you may want to contact Microsoft CSS
    | > directly.
    | > | > | > Please
    | > | > | > | > check http://support.microsoft.com for regional support
    phone
    | > | > numbers.
    | > | > | > | >
    | > | > | > | > Any input or comments in this thread are highly appreciated.
    | > | > | > | > =====================================================
    | > | > | > | >
    | > | > | > | > This posting is provided "AS IS" with no warranties, and
    | > confers
    | > | > no
    | > | > | > | > rights.
    | > | > | > | >
    | > | > | > | > --------------------
    | > | > | > | > | From: "PR" <>
    | > | > | > | > | Subject: Use Outlook 2003 from SBS2003
    | > | > | > | > \\servername\ClientApps\outlook2003
    | > | > | > | > | Date: Wed, 16 May 2007 15:12:39 -0700
    | > | > | > | > | Lines: 16
    | > | > | > | > | X-Priority: 3
    | > | > | > | > | X-MSMail-Priority: Normal
    | > | > | > | > | X-Newsreader: Microsoft Outlook Express 6.00.2900.3028
    | > | > | > | > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
    | > | > | > | > | X-RFC2646: Format=Flowed; Original
    | > | > | > | > | Message-ID: <>
    | > | > | > | > | Newsgroups: microsoft.public.windows.server.sbs
    | > | > | > | > | NNTP-Posting-Host: 209-234-154-253.static.twtelecom.net
    | > | > | > 209.234.154.253
    | > | > | > | > | Path:
    | > | > | > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
    | > | > | > | > | Xref: TK2MSFTNGHUB02.phx.gbl
    | > | > | > microsoft.public.windows.server.sbs:37295
    | > | > | > | > | X-Tomcat-NG: microsoft.public.windows.server.sbs
    | > | > | > | > |
    | > | > | > | > | Anyone,
    | > | > | > | > |
    | > | > | > | > | Having tried and failed, I ask:
    | > | > | > | > | Is it possible to install Outlook 2003 from the
    | > | > | > | > | (\\servername\ClientApps\outlook2003\setup.exe
    | > | > | > | > | Having tried and faiHaving tried and failed, I ask:
    | > | > | > | > | Can I use Outlook 2003 from SBS2003 on computer that I
    have
    | > not
    | > | > | > joined
    | > | > | > | > to
    | > | > | > | > | the domain, (but which would be counted towards CALs etc).
    | > | > | > | > |
    | > | > | > | > | If so how? I'm prompted for the product key, have tried
    | > those
    | > I
    | > | > | > recieved
    | > | > | > | > | with my SBS2003 package, but no luck.
    | > | > | > | > |
    | > | > | > | > | Thanks.
    | > | > | > | > |
    | > | > | > | > |
    | > | > | > | > |
    | > | > | > | > |
    | > | > | > | >
    | > | > | > |
    | > | > | > |
    | > | > | > |
    | > | > | >
    | > | > |
    | > | > |
    | > | > |
    | > | >
    | > |
    | > |
    | > |
    | >
    |
    |
    |
     
    Terence Liu [MSFT], May 22, 2007
    #16
    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.