Home

Results 1 to 2 of 2

Thread: Specify server or don't - latest word?

Hybrid View

  1. #1
    Join Date
    Feb 2008
    Posts
    60

    Specify server or don't - latest word?

    Hello everyone,

    It's been a really long time since I worked on something like this. I just finished a server migration and the workstations at the site in question have the old server saved in the advanced login properties of the default profile. I know how to change this with a quick zenworks app to change the registry key. What I want to know is, should I be changing this to the new local server or just leave it blank. This is a small campus location with a single (once the old one is removed) server, SLP being pushed via DHCP (DA's are remote), local partition replica on the server. Should I need this server specified in the login dialog, if I don't have it should the login be slower. If the wan link gets disconnected will there be more risk of login problems if it can't contact the DA's. Some users may be on different subnets from the server. Thanks for your best practice advice.

  2. #2
    Dave NNTP User

    Re: Specify server or don't - latest word?

    jshorr scrawled:

    >
    > Hello everyone,
    >
    > It's been a really long time since I worked on something like
    > this. I just finished a server migration and the workstations
    > at the site in question have the old server saved in the
    > advanced login properties of the default profile. I know how
    > to change this with a quick zenworks app to change the
    > registry key. What I want to know is, should I be changing
    > this to the new local server or just leave it blank. This is
    > a small campus location with a single (once the old one is
    > removed) server, SLP being pushed via DHCP (DA's are remote),
    > local partition replica on the server. Should I need this
    > server specified in the login dialog, if I don't have it
    > should the login be slower. If the wan link gets disconnected
    > will there be more risk of login problems if it can't contact
    > the DA's. Some users may be on different subnets from the
    > server. Thanks for your best practice advice.


    The client will look for the closest server to enable a quicker
    login. Best advice is test it out on a workstation with no
    server specified and see how it goes.

    If the WAN links go down, the replica stored on that server
    should take care of any logins.

    Users on different subnets should be able to connect if you
    specify the server. Bare in mind, if the workstation can't ping
    the server, the login will obviously fail.

    --


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •