|
|
|
re: Cannot Log In to Server...and other things
Thursday, December 28, 2006 at 6:07 am
Windows Server 2003 Annoyances Discussion Forum
Posted by PaulMun75
(1 messages posted)
Could it be that you've blocked yourself with group policy or something? Maybe you've
simply lost connection with your authenticating domain controller? You can restore
admin password if you have local administrative account and interactive logon is
permitted within Security policies on your server. Try following the steps noted
in article (http://www.petri.co.il/reset_domain_admin_password_in_windows_server_2003_ad.htm).
Now about your 'new life' after restoring the password. Practically there's no problem
with managing your network yourself without need to invite somebody from the outside.
You can do the trick he does with a desktop management software. A good primer is
Scriplogic's Desktop Authority, Microsoft System Management Server, etc. We use Desktop
Authority (www.scriptlogic.com) and can manage a big company infrastructure with
a pretty small presonell. You've probably heard about Microsoft IntelliMirror technology
and GPO (http://technet2.microsoft.com/windowsserver/en/technologies/featured/gp/default.mspx).
These all solutions allow administrators to manage thier client desktops, user and
corporate environment with one-to-many management. That is I can create a set of
settings for my users and a set of rules that will define when, where and who of
my users will receive wich type of settings when he will log on to his computer.
The core difference between these two tools (GPO and desktop management tools) lies
within usability and easiness of management. GPO requires using WMI-scripting to
implement specific tasks. Basic task can be done with GPEditor though and doesn't
require extra scripting. Wereas with desktop management tool you can do complex task
without using scripting.
For example, you setup your corporate proxy server. Now you want to set its URL to
internet settings on all user machines. And then you maybe need want leave some users
or whole organisation units without these settings. With Desktop Authority I can
exclude needed users all OUs from being affected by this change.
Another standart task is software deployment. Usually I create one 'standard' task
for all domain and many individual task that I assign on per-OU basis. For example
all users within my corporate get Microsoft Office deployed on thier machines.
And now we got another task of how to set office applications for user environment.
All of my domain users get Outlook client. But I want also setup mail settings to
connect client to its Exchange Server. And I can do that individually. Each user
would have its personal mail settings and mailboxes when he will log on to domain.
The second standart task is print management. For example you can set user to have
nearest network printer connected to him and set as default. Pretty simple task from
the point of 'need' but hard to implement manually.
Another valuable thing that creates a problem within the corporate if you miss it
is power management. Usually you cannot force all people to shut their machines down
when they leave thier workplaces. That creates a problems with big bills (if you
have serval offices). Additionally it create problems for security because some users
even do not lock thier machines untill you'll implement the automation of this functionality.
With the same Desktop Authority I can set schedule windows when Desktop Authority
will check for user inactivity. For example if user is inactive for half a hour after
8 PM we can shut down his computer and run software update on shutdown. Or we can
simply lock user machine if he is inactive for 10 minutes within his workday.
When I talk about automation provided by desktop management tools this doesn't means
that you wouldn't be able to script your porgrams if you need some extra procedures
with configuration. For example Desktop Authority is based on KIX scripting technology
(http://www.kixtart.org/). So when we need to implement a really specific configuration
we can use self-written scripts that will add some push to existing functionality.
On Thursday, December 14, 2006 at 9:29 am, Matt D wrote:
>Recently we added a server to our small construction office (5 people). We had
a
>guy come in, order everything, set it up, etc, etc. Well he sucked, never called
>us back and only half of our stuff works so we are trying to tweak it ourselves.
> So I have a couple questions. First off I logged into the Server through my computer
>as the Adminstrator to try to set up VPN Access. After I logged out, and try to
>log back in as myself it will not work, like I have a wrong password (which is not
>the case)....any idea how to fix this? The only way to use my computer now is for
>me to log into my laptop as the administrator, I cannot log into the server as the
>administrator from my laptop again either...
>
>Second, We need to set up a back up system. I bought 10 20/40 tapes for the internal
>drive. I noticed on the bill the server came with Yosemite Backup SBS, is this
better
>then the standard windows software I can use?
|
All messages in this thread [show all]
 |  | re: Cannot Log In to Server...and other things (PaulMun75: Thu, Dec 28, 2006, 6:07 am) |
| |
| |
Return to the Windows Server 2003 Discussion Forum
|
|
|
|
