You're allowed to kick and scream along the way, though, right?

Joe Heaton
Employment Training Panel


-----Original Message-----
From: Erik Goldoff [mailto:egold...@gmail.com] 
Sent: Wednesday, July 01, 2009 1:55 PM
To: NT System Admin Issues
Subject: RE: Terminal Services question

Yep, I've seen both sides of the fence ... Some corporate setups where
they
did not want to budget for remote equipment, and executive level
insisted on
enabling remote access for POE ... Sometimes you just have to do what
the
business decides 



Erik Goldoff
IT  Consultant
Systems, Networks, & Security 


-----Original Message-----
From: Charlie Kaiser [mailto:charl...@golden-eagle.org] 
Sent: Wednesday, July 01, 2009 4:29 PM
To: NT System Admin Issues
Subject: RE: Terminal Services question

For me it's the opposite. I only allow approved machines/users to get
remote
access of any kind. No POE at all unless approved at C level...

It's all in how you define your criteria, I guess.

***********************
Charlie Kaiser
charl...@golden-eagle.org
Kingman, AZ
***********************  

> -----Original Message-----
> From: Erik Goldoff [mailto:egold...@gmail.com]
> Sent: Wednesday, July 01, 2009 12:55 PM
> To: NT System Admin Issues
> Subject: RE: Terminal Services question
> 
>  privately owned equipment is a presumption on my part based on 'home'
> access ... Although some agencies deploy govt owned equipment, they're

> normally issued along with a vpn/remote access solution built in, at 
> least with my experience with Federal govt...
> 
> 
> 
> Erik Goldoff
> IT  Consultant
> Systems, Networks, & Security 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to