RE: Outlook client setup
- From: "mrmikefm" <mrmikefm@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 7 Dec 2005 09:44:02 -0800
What I finally found by reading through all the garbage in the in the notepad
files that logged the setup, was that it couldn't find the install file. I
then attempted to find it the same way that the computer did. I also could
not. So, I shared the "client apps" folder, which either wasn't previously
shared, or had it sharing taken away. As soon as I turned on sharing on that
folder, and ran the wizard to join the domain again. It worked just fine.
I have no idea if that folder is/was supposed to be shared or not, but that
worked for me.
Thanks for your assistance.
Michael Dutcher
""Brandy Nee [MSFT]"" wrote:
> Dear Customer,
>
> Thank you for posting back!
>
> From your description, I understand that you newly setup a SBS 2K3 Server
> and brought it to new location, and then you joined some Windows XP Prof
> into SBS Domain.
>
> [Important]: In SBS 2003, we do not support Windows XP Home Edition clients
> since they cannot be joined into the domain and therefore cannot be managed
> centrally. They also cannot utilize also most all the SBS 2003 and domain
> features. However if you only want the XP HE clients to be able to access
> shared resources on the network, the answer should be Yes as long as the XP
> HE users have the domain user accounts with the appropriate permissions
> over the shared resources.
>
> Actually we recommend you upgrade to Windows XP Pro and join it to the
> domain.
>
> Please see my following steps to assign Outlook 2003 on client
> workstations:
>
> 1. Expand to Server Management\Standard Management\Client Computers. On the
> right pane, click Assign Application to Client Computers. Run the Assign
> Application Wizard.
>
> 2. Proceed to the Page of Client Applications, click Edit Applications. You
> are in the Set Up Client Applications Wizard.
>
> 3. Proceed to the page of Available Applications, click Add.
>
> 4. In the blank under Location of setup executable for this application,
> type the following command:
>
> "\\Yourdomain\ClientApps\Outlook2003\setup.exe"
> Transforms="\\Yourdomain\Clients\Setup\sbsdefault.mst" /qn
> Reboot=ReallySuppress /wait INSTRALLLOCATION="%location%" /Lv
> "%temp%\verbose.log".
>
> 5. Finish rest of the Set Up Client Applications Wizard and the Assign
> Application Wizard.
>
> 6. Test the issue again.
>
> If the issue persists, please help to gather following information for
> further research:
>
> a. Does this issue occur on several client workstations or all client
> workstations?
>
> b. What is the edition of the problematic client workstations, Home or
> Prof?
>
> c. Please capture a screen shot for "it just says that it didn't install".
> How do you know it does not install?
>
> Please take your time to perform the steps above and collect the
> information for us to troubleshoot your issue. I am looking forward to
> hearing from you!
>
> Best regards,
>
> Brandy Nee
>
> 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.
>
>
>
> --------------------
> >Thread-Topic: Outlook client setup
> >thread-index: AcX6qvXYzOqFsw46QkOsBrje9booBA==
> >X-WBNR-Posting-Host: 64.146.131.31
> >From: "=?Utf-8?B?bXJtaWtlZm0=?=" <mrmikefm@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >References: <440D8CEA-E70D-4F94-94D5-D33EDBC16ED2@xxxxxxxxxxxxx>
> <j9fgDFj#FHA.3152@xxxxxxxxxxxxxxxxxxxxx>
> >Subject: RE: Outlook client setup
> >Date: Tue, 6 Dec 2005 13:21:02 -0800
> >Lines: 129
> >Message-ID: <665AC548-4472-482E-BFD3-3FA8B9FE5970@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:228185
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >I use the user and computer setup wizard just like I always do. I add the
> >user that I want and the computer that I want. Then when I go through the
> >connect Computer through the web interface, it all seems to work fine, but
> it
> >never installs Outlook. I don't get any error messages, it just says that
> it
> >didn't install. I can't seem to find what is happening by reading the
> >notepad files that explain what happened during setup that would cause
> this
> >to happen.
> >
> >A little more background. I setup the server at another location, and
> then
> >moved it into the office. I then connected all the xp pro machines at
> that
> >time. I had two xp home machines, that the actual office owner said that
> he
> >would install xp pro on later. That's when I came back and attempted to
> add
> >the systems to the domain just like the rest of them. All seemed to go
> well
> >except they wouldn't install Outlook. And that seems to be the only
> problem.
>
>
.
- Follow-Ups:
- RE: Outlook client setup
- From: "Brandy Nee [MSFT]"
- RE: Outlook client setup
- References:
- RE: Outlook client setup
- From: "Brandy Nee [MSFT]"
- RE: Outlook client setup
- From: mrmikefm
- RE: Outlook client setup
- From: "Brandy Nee [MSFT]"
- RE: Outlook client setup
- Prev by Date: adding a new member server question, should/shouldn't I.
- Next by Date: Re: When will password policy take effect
- Previous by thread: RE: Outlook client setup
- Next by thread: RE: Outlook client setup
- Index(es):
Relevant Pages
|
Loading