RE: 2008 server crash!

2010-07-08 Thread robbonfig...@gmail.com
I'm curious, what other data do you have on your Domain Controller other than 
AD?
-Original Message-
Date: Thursday, July 08, 2010 7:36:28 pm
To: "NT System Admin Issues" 
Cc: "Ziots, Edward" 
From: 
Subject: RE: 2008 server crash!

I don't care about active directory on the server.  I am concerned about the 
DATA on the drive.




 "Ziots wrote: 
> Honestly, If you have another DC, then I would follow the /forceremoval of a 
> Domain Controller per..
> 
> http://support.microsoft.com/kb/555846 (Covers Win2k3 and below)
> 
> http://www.petri.co.il/delete_failed_dcs_from_ad.htm (Step by Step to remove 
> the DC)
> 
> HTH
> 
> Z
> 
> Edward E. Ziots
> CISSP, Network +, Security +
> Network Engineer
> Lifespan Organization
> Email:ezi...@lifespan.org
> Cell:401-639-3505
> 
> 
> -Original Message-
> From: jesse-r...@wi.rr.com [mailto:jesse-r...@wi.rr.com] 
> Sent: Thursday, July 08, 2010 7:27 PM
> To: NT System Admin Issues
> Subject: 2008 server crash!
> 
> I have a Windows 2008 x32 server (HP Proliant ML310 G5p) that just crashed.  
> When booting, its giving me a C00218 error (the registry cannot load the 
> hive, etc.).  The server is also a domain controller.
> 
> Few things to note:
> 1. I have other


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~


RE: Single Live Comm Server 2005 upgrade to OCS 2007

2010-05-20 Thread robbonfig...@gmail.com
It's been a couple of years since I did this...but from what I remember I'm 
pretty sure it was basically a swing migration. There was documentation for it 
somewhere though.

-Original Message-
Date: Thursday, May 20, 2010 8:50:07 pm
To: "NT System Admin Issues" 
Cc: "Exchange list (exchangel...@lyris.sunbelt-software.com)" 

From: "Bob Fronk" 
Subject: Single Live Comm Server 2005 upgrade to OCS 2007

All the deployment documentation involves much more complicated Live 
Communication Server setups with multiple directors, etc.

I have a single Live Communication Server 2005 server which is used 99.9% for 
IM only.  We need to move to Office Communication Server 2007.  Currently I 
don't need more than a single server as the main use will remain just IM, but 
we will add other services soon.

Has someone performed a simple upgrade like this?  Is it just as simple as 
installing OCS 2007 and moving the users?  Or do I need to do a more 
complicated install with multiple OCS 2007 servers with different roles?

--

Bob Fronk
b...@btrfronk.com


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~


Re: TS Gateway Setup

2010-02-02 Thread robbonfig...@gmail.com
I am setting up a TS Gateway right now with Smart card access. It's working 
from my desk to the DMZ to the terminal server. I haven't opened up the 
firewall yet to try it from the internet though.

-Original Message-
Date: Tuesday, February 02, 2010 11:03:40 am
To: "NT System Admin Issues" 
From: "Richard Stovall" 
Subject: Re: TS Gateway Setup

I moved away from the old-fashioned Cisco VPN client a while ago and haven't
looked back.  For a small environment, TS Gateway is so easy to setup that
it definitely merits consideration among the many options available.  And if
you're already using Terminal Services you basically get it for free if
you've get the licenses.

Why do you require that the remote session run in a browser?  I'm not saying
it's a bad idea at all, I'm just wondering if it's necessary.  AFAIK, to use
vanilla TS Gateway (I think it's now called Remote Desktop Services in 2008
R2), you're going to be running the RDClient (mstsc.exe) on the the remote
machine or an ActiveX control (mstscax.dll?) to keep it in the browser.  Is
the browser context more secure?

Regarding the use of SecurID, I looked for a long time for a way to use
either one time passwords or smart cards from several vendors with TS
Gateway and never found anything that worked.  Several companies said it
would, but none of them really understood TS Gatewa


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~