Re: Software Rollout

Tech-Archive recommends: Fix windows errors by optimizing your registry

I take it that you do not see a little black box running when you log
in to the domain? I edit that batch file all the time to map domain
wide drive letters to shares on the server. At an account that is
working properly I go to the user's properties. Click the profile tab
and SBS_LOGN_SCRIPT.BAT is in the logon script box. If it is missing
from there then someone edited somethng to prevent it from
auto-populating when creating new users. I do not know where that
comes from though.

On 6 Mar 2007 16:40:01 -0800, "Matt Walker" <MattPWalker@xxxxxxxxx>
wrote:

Thanks again for another excellent reply. I've found the
sbs_login_script.bat file and it does indeed contain on the first line
\\SERVERNAME\Clients\Setup\setup.exe /S SERVERNAME (different exe name
to the one you mentioned). I ran this command from the run box and
low and behold... it installed outlook. So I guess I could conclude
that wherever this batch file is meant to be set, it has been removed/
changed. Any ideas where I could check which logon script (if any is
now being used by users logining in?

Thanks Again.

Matthew



On Mar 6, 10:21 pm, Jim Behning SBS MVP
<jimbehn...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Outlook and use of Outlook is part of your SBS cals.

If something did not install then just do the
\\servername\clientapps\and find the Outlook install.

You could compare the sbs_login_script.bat file on your server with a
good one. The frst line shoudl say something like
\\sbsservername\Clients\Setup\SBSCLNT.exe /s TCFSBS For that line to
really run I think you need to be an administrator of the workstation.
you can run that line from the run box to see if it works as another
troubleshooting method. I have seen the path be incorrect after an
upgrade or if someone moved the clientapps folder and goofed up the
share name.

On 5 Mar 2007 21:38:07 -0800, "Matt Walker" <MattPWal...@xxxxxxxxx>
wrote:

Thanks for your reply,

I did add the computer through server manangment then used the
connectcomputer link to connect them, however outlook did not
install. According to the previous guy it worked for him, I didn't
change anything in AD or policies that I'm aware of. Where would I
start to look to see if the other guy accidently removed the automatic
installation of outlook.

Another question is: does a CAL pack include licenses of outlook? The
boss here seems to think we bought additional licenses of outlook but
I can only find a 5 CAL pack and no record of separate purchases of
outlook.

Thanks Again

On Mar 5, 10:51 pm, Jim Behning SBS MVP
<jimbehn...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Are you adding new computers from Server Management on the SBS? Second
step is to join the computer to the domain usinghttp://sbsservername/connectcomputer. This should install Outlook and
do a litle preconfiguration.

The Outlook install is in \\sbservername\clientapps. You can start-run
and dig around to manually install.

On 4 Mar 2007 23:20:47 -0800, MattPWal...@xxxxxxxxx wrote:

Good Afternoon,

I've recently joined a company where I've been asked to fill a jack of
all trades Admin type position. Coming from a SOHO pc technician
background I've a passing familiarity with some basic SBS 2003 usage.
I apologise in advance for my lack of familiarity with basic concepts
(I'm reading books to try and catch up ;)).

Here's the situation: It seems that someone before me had rolled out
outlook2003 from the server whenever a new computer was added to the
network using the web based connectcomputer wizard. However, I've
added several pcs since I've started with the company and no software
has been rolled out.

Can someone help me locate where the settings for such software would
live and why it might have stopped.

Cheers

Matt Walker

.

Relevant Pages

  • Re: DST update for Exchange 2003 and Outlook 2003
    ... it named the batch file MSEXTMZ_1.BAT; ... Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe. ... MsExTmzCfg will create a subfolder named for your Exchange Server, ... "If you want to try it out on only a few mailboxes at first, ...
    (microsoft.public.exchange.admin)
  • Re: Shared fax
    ... I tried on one workstation to install an outlook 2003 and connected to the ... > What is your client computer's Outlook version? ... > Integration\Windows Small Business Server 2003\Logs''. ...
    (microsoft.public.windows.server.sbs)
  • RE: Update Outlook
    ... Thank you for posting in the SBS newsgroup. ... 2003 Server, an administrative installation of Outlook 2003 is installed at ... In addition, please don't install Outlook ...
    (microsoft.public.windows.server.sbs)
  • RE: KB885918 SBS2003 SP1 Install Error
    ... We can not install Outlook 2003 on the SBS 2003 server ... client workstations rather install outlook on the server box. ... In the following website you can find many useful resources related to SBS ...
    (microsoft.public.windows.server.sbs)
  • RE: DST update for Exchange 2003 and Outlook 2003
    ... "On the terminal server, run the TZMOVE.EXE that you downloaded. ... install a file named TZMOVE.EXE along with a TZMOVE.DLL under your Outlook ... On the terminal server you mentioned, log in as a user with full mailbox ...
    (microsoft.public.exchange.admin)