Michael Lueck wrote:
On Mon, 19 Jul 2004 21:31:03 -0500, Paul Gienger wrote:
Rather than monkey with each client, just don't define a [profiles]
share. I'll check one of our setups tomorrow, we have a site with no
roaming there (for now).
I did not have a roaming share defined and Win2K
Michael Lueck wrote:
Also remember, every change you make to a client is one more thing to
screw up
If you're going to compute that way, then put the computer back in the
box and leave it on the client's desk and tell them to never open the
box! ;-)
When doing sysadmin isn't your only job,
Paul Gienger wrote:
So do us a favor and let us in on what you're using in case anyone
else wants to know...
FWIW, we took on a temp (someone we know who was 'between jobs') to
do a rollout of XP. He introduced us to Symantec Ghost which seems
quite a useful tool. I don't think it cost us much,
On Tue, 20 Jul 2004 07:51:34 -0500, Paul Gienger wrote:
So do us a favor and let us in on what you're using in case anyone else
wants to know...
In many areas I develop my own for use within LDS consulting.
Vendor tools I care to suggest would be Prism Pack from New Boundary
Technologies on
So sorry to hear you end up with off-site machines with no remote access.
Unacceptable in my book. VPN back door, SSH, NetOp, and electronic software
distribution of course.
Actually, this usually happens only for a couple weeks to months before
the office gets in the VPN. In this case,
Wow! The blank logon path worked! Thanks so much!!
-jag
On Tue, 2004-07-20 at 06:31, Paul Gienger wrote:
Michael Lueck wrote:
On Mon, 19 Jul 2004 21:31:03 -0500, Paul Gienger wrote:
Rather than monkey with each client, just don't define a [profiles]
share. I'll check one of our
