Harm in making an unknown configured ISA server joining the domain.

[multiband8303]

As explained in a previous thread... A contractor got half way through configuring the ISA Server 2004, nothing malicious would be on it by any means. The reason why he was escorted out was not related to his work....long story.

However, I do not know how far he got into the configuration, and during the next 2 weeks I will be doing much reading on ISA Server 2004.

However, for the ease of management, I would like to add this to the domain - obviously I have no GPO's (yet) that point my client computers to use the ISA server as a proxy (which when in production will be its primary intent) however, do you see any other harmful impact of this joining the domain?

Just some helpful input would be great.

 

[yinan]

Do not do this. Once it joins the domain it could start to do very bad things.

Reformat and start over. It is not that hard to set up ISA. I could prolly do it in less than a day.

 

[multiband8303]

Originally posted by: yinan
Do not do this. Once it joins the domain it could start to do very bad things.

Reformat and start over. It is not that hard to set up ISA. I could prolly do it in less than a day.

From the looks of it - it is extremely straight forward.

 

[Smilin]

"Your" Domain is a term subject to change. Don't do it.

 

[Brazen]

Told you so 😀. Besides, if he didn't get through configuring it, it would probably be just as easy (or easier) to start over rather than figure out what he did and did not get done.

Also, after he was "dismissed" if the box was accessible from the internet, he could have gone in afterward and done some maliciousness in retaliation.