[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 348
  • Last Modified:

Automatically setup outlook upon login

I am running SBS 2003 with Exchange.  Is it possible to automatically set up outlook to use the user's exchange account upon login?  For example, without doing any set up, I would like to login to PC1 as "user1" and open outlook to my exchange account without any configuration.  Same for "user2" and for user1/user2 on "PC2".
0
ejoech
Asked:
ejoech
  • 5
  • 4
  • 3
  • +1
2 Solutions
 
The_IT_GarageCommented:
Yes this is possible if you use an Office or Outlook resource kit and then you can place the comands in a login script so it's configured for each macnhine you log in to.
0
 
ZadkinCommented:
It's part of the SBS package.  If you use (wizardwize) registered users and computers, Outlook is installed and you are connected to Exchange at login.
0
 
ejoechAuthor Commented:
Hmm.  I am not connected to Exchange at login..not sure how to do this.  I suppose I am looking more for if/how, not just if.  What are the commands? Thanks..
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
ZadkinCommented:
The general way:
The outlook configuration is user bound on each computer.  If you set up outlook through outlook-menu-tools-e-mail accounts once, next time you log in on the PCX as user Y it will be OK.  

SBS way:  Add user and computers trough the management console of the SBS server
0
 
The_IT_GarageCommented:
That is not necessarily correct. If you use the resource kit
http://office.microsoft.com/en-us/assistance/CH011496861033.aspx

You can put an entry in the login script that will autoconfigure Outlook, specifically using the maintenance wizard:
http://office.microsoft.com/en-us/assistance/HA011402391033.aspx

Once you get everything configured the line in the logn script will look similar to this:
\\SERVER\NETLOGON\MAINTWIZ.EXE \\SERVER\NETLOGON\FILENAME.CMW

Once you get it right the Outlook settings follow the user, even if the user hasn't opened up Outlook on a machine before.

Additional resources:
http://www.slipstick.com/problems/defaultacct.htm
http://www.slipstick.com/outlook/prftips.htm

Also Googling for .PRF will return additional info. Same for Googling MAINTWIZ.EXE
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
The IT Garage... I must tell you that your solution is entirely not correct with regards to Small Business Server.

This is handled automatically if the server and workstations have been installed and configured correctly.
Zadkin is quite right about this.


ejoech...  did you add your workstations using the http://<servername>/connectcomputer method?  

Also, can you please post an IPCONFIG /ALL from the server and a workstation?  That will help in determining where you currently stand.

Jeff
TechSoEasy
0
 
The_IT_GarageCommented:
Excellent info, I stand corrected.
0
 
ejoechAuthor Commented:
I apologize for not responding to this earlier.  I must not have added the workstations properly then.  I just joined the workstations to the domain..and then they showed up in the "Client Computers" of Server Management.

Here is an ipconfig of the server..I won't be able to get a workstation until after the work day.

Windows IP Configuration

   Host Name . . . . . . . . . . . . : WASVR
   Primary Dns Suffix  . . . . . . . : walpoa.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : walpoa.local

Ethernet adapter Server Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-14-22-7B-4D-3C
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.0.10
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.10
   Primary WINS Server . . . . . . . : 192.168.0.10
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
No prob... fyi, you can use PSExec to get an IPCONFIG off a remote workstation:
http://www.sysinternals.com/Utilities/PsExec.html

Jeff
TechSoEasy
0
 
ejoechAuthor Commented:
Here is the IPCONFIG /all of a workstation.  I have been out of town on business, I apologize for taking so long to reply!

H:\>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : wa1
        Primary Dns Suffix  . . . . . . . : walpoa.local
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : walpoa.local
                                            walpoa.local

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : walpoa.local
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
        Physical Address. . . . . . . . . : 00-13-20-D0-01-27
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.0.11
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
        DHCP Server . . . . . . . . . . . : 192.168.0.10
        DNS Servers . . . . . . . . . . . : 192.168.0.10
        Primary WINS Server . . . . . . . : 192.168.0.10
        Lease Obtained. . . . . . . . . . : Wednesday, May 10, 2006 3:37:15 AM
        Lease Expires . . . . . . . . . . : Thursday, May 18, 2006 3:37:15 AM
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Okay all of that is fine... so if you didn't add the workstations correctly then you need to follow these steps to correct the problem:

The following needs to be done with the client machine:
1.  Log in with THAT machine's LOCAL administrator account.
2.  Unjoin the domain into a WORKGROUP
3.  Change the name of the computer
4.  Delete or rename the following directory C:\Program Files\Microsoft Windows Small Business Server\Clients
5.  Ensure that DHCP is enabled and there are  no manually configured network settings
6.  Reboot

Then on the server, from the Server Management Console:
1.  Remove the client computers if it still shows in the Client Computer screen on the Server Management Console
2.  Add the client with it's NEW name using the Add Computer wizard

Then, go back to the client machine and join the domain by opening Internet Explorer and navigating to http://servername/connectcomputer

Jeff
TechSoEasy
0
 
ejoechAuthor Commented:
I apologize for dragging this thread out so long.  I've had other things to do and have not worked for this client in a while.  Anyway, I thank everyone for your help.  Another helpful solution from the great people of experts-exchange.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You're quite welcome... but I'm not really "OF" Experts-Exchange...   I may be "AT" Experts-Exchange... just as you are.    I know... it may be nitpicky... but since the experts don't work for EE, I thought I'd clarify.  :-)

Jeff
TechSoEasy
0
 
ejoechAuthor Commented:
Yes, I understand.  I meant it as we are all of experts-exchange because we all frequent here.  Thanks though. :)
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 5
  • 4
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now