Re: SBS 2003 Server down. what would you do?

I never thought about that, and I've never logged into my LAN with cached
credentials for over the 10 hour TGT life. But I've had remote users log
into laptops with cached credentials for days - probably over a week. So
I'm confident you'll get into the workstations, but I wouldn't even venture
a guess as to what will happen with the server.

Allen - what happens when you log into your desktop with your domain
credentials and try to access the member server?


"kj" <kj@xxxxxxxxxxx> wrote in message
news:%2308ek4cXGHA.1084@xxxxxxxxxxxxxxxxxxxxxxx
Dave,

Doesn't the 10hr TGT expiration negate network resource access?

--
/kj
"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:OAGOC%23bXGHA.1084@xxxxxxxxxxxxxxxxxxxxxxx
No, with the cached credentials, users should be able to access whatever
they can while the SBS is available, other than things hosted on the SBS
itself. As for DHCP, it depends on when the leases expire. I just
looked on my workstation and I've got until the 19th, so you might get
lucky in that regard.

I would try the cached credentials thing. Just log into your workstation
as you normally do, and see if you can access the member server. You
should be able to.

Accounts use SIDs, not actual usernames. So if you have a user ABC, and
you create a new domain controller or reinstall SBS from scratch with
user called ABC, the server will use the SID, not the username, and it'll
consider these to be two separate users. (SID = security identifier).
So the answer to your response to Les is no, you can't bring up a new box
with the same server and domain names - they'll still be considered
different. Unless you want to create all new user profiles and reconnect
all the desktops, etc. your only real option is to restore the SBS from
backup.



"AllenM" <ghost@xxxxxxxxxxxx> wrote in message
news:%23Tww8gbXGHA.3532@xxxxxxxxxxxxxxxxxxxxxxx
Yes you are allowed to login into the domain with cached credentials.
But how am I going to access the member server? My DHCP server is also
down with SBS. I can input a static IP but will need to apply new groups
and permissions right?


"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:eCTFgbaXGHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
With the SBS down, won't the desktops allow login with cached
credentials? That would give access to the member server.

You could manually set up a default gateway pointing to your DSL modem
or whatever device your Internet connects to, but remember you will be
running without ISA and possibly without some of the AV protection
provided by the SBS.



"AllenM" <ghost@xxxxxxxxxxxx> wrote in message
news:%23gvHMxZXGHA.3656@xxxxxxxxxxxxxxxxxxxxxxx
OK I'm in a no outs situation right now. My SBS 2003 Premium server is
down. Literally. Motherboard is fried. Server is out of warranty
however I was able to renew the warranty but it will not be processed
for 24-48 hours. Best case scenario to be back up and running looks
like Friday. In the meantime my workers are out of business. No
network, email or internet access. I do not have a backup server. We
are a small company and we only have 2 servers. The SBS server and a
Windows 2003 server that handles just about everything else the SBS
server doesn't. What can I do? Here's what I've thought may be a
temporary solution.

Build another SBS 2003 server of course. I do have full tape backups
but unfortunately that resides on the SBS server including the
hardware. I just need a DC so people can log on and access the other
Windows 2003 server. Email would be nice but not practical as far as
restoring. I guess what I'm trying to say is that the SBS 2003 server
will be down at least until Friday if not longer depending on when the
warranty will be active and how fast the tech can get dispatched with
a new motherboard. That is a given. Is it worth the effort to build
another SBS server? I'm not worried about importing and restoring the
existing FSMO roles and policies and ADUC accounts. I can open the
ppermissions to Everyone. As far as new user accounts that is not a
problem either as were only talking about maybe a dozen at the most.
What would you do and what do you suggest. And yes I already know most
of my problems could have been avoided with a backup DC but let's not
get into any "you should have" bashing. thanks.












.

Relevant Pages

  • RE: Server Error in /Backup Application.
    ... Thank you for posting in SBS newsgroup. ... Regarding the error you receive when you use the Monitoring and Reporting, ... 823379 You receive a "Server Error in '/' Application. ... Monitoring site, Backup site, and Companyweb each has their own Web.config ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS Backup problems
    ... other application service) installed on the SBS 2003 server? ... So I would not think this could be the reason for backup ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Server Management Backup Page Not Found
    ... reinstall backup and monitoring components. ... Perform a full backup of the SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Backup failing
    ... I understand that you encounter error 800423f4 when trying to backup SBS ... volume by using the Volume Shadow Copy service in Windows Server 2003 ... I've re-registered the VSS DLLs. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS Backup problems
    ... Hardware Compatibility List for Windows Server 2003. ... I would like to suggest you install Exchange 2003 SP1 on the SBS ... Microsoft is providing this information as a convenience to you. ... Be sure to make a full backup of SBS server immediately before and after ...
    (microsoft.public.windows.server.sbs)