<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: XP in a 95/98 network in Operating System - Microsoft</title>
    <link>https://community.hpe.com/t5/operating-system-microsoft/xp-in-a-95-98-network/m-p/2776724#M1931</link>
    <description>Hello,&lt;BR /&gt;       Well we ran in to similar issues where I work.  First I'm assuming you do have an NT domain controller on an NT 4 machine.  When the XP workstations we've given these users local Admin (just added their domain group to power users) And since the XP machine is a member of the domain, IS team has Admin to the machines with out having accounts thus fixing the issue with end-users being able to remove IS users.  With the users in the local admin group they can add and remove drivers and software.  I know this sounds like a security problem, but with 9X and ME all the users (by default) have the software.  IF you do not have a Domain, I would configure one of your machines to be a Domain controller this would help you push security polices to all users.  I hope this helps and this should be cost effective as well.  If it does help please don't forget the points.</description>
    <pubDate>Wed, 31 Jul 2002 17:05:31 GMT</pubDate>
    <dc:creator>John-Thomas Gaietto</dc:creator>
    <dc:date>2002-07-31T17:05:31Z</dc:date>
    <item>
      <title>XP in a 95/98 network</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/xp-in-a-95-98-network/m-p/2776723#M1930</link>
      <description>We've got 80 PCs all running 95/98/ME, with several NT4 file servers.  Users need to log in to NT to get access to the file servers but as you might guess, the PCs themselves are not secure.&lt;BR /&gt;&lt;BR /&gt;We've recently introduced a few PCs running XP PRO and we're having an awful time.  It seems that you need to be an admin on the PC to install any software etc. something which our users are allowed to do, for the most part.  Like adding Acrobat reader, that sort of thing.&lt;BR /&gt;&lt;BR /&gt;However, admin privileges allow the user to mucky-muck with other stuff, including removing the MIS staff's account on the PC, etc.&lt;BR /&gt;&lt;BR /&gt;How are other companies resolving this?  We don't have the budget to make the whole place an XP network.&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Jul 2002 14:16:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/xp-in-a-95-98-network/m-p/2776723#M1930</guid>
      <dc:creator>Fred Martin_1</dc:creator>
      <dc:date>2002-07-31T14:16:42Z</dc:date>
    </item>
    <item>
      <title>Re: XP in a 95/98 network</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/xp-in-a-95-98-network/m-p/2776724#M1931</link>
      <description>Hello,&lt;BR /&gt;       Well we ran in to similar issues where I work.  First I'm assuming you do have an NT domain controller on an NT 4 machine.  When the XP workstations we've given these users local Admin (just added their domain group to power users) And since the XP machine is a member of the domain, IS team has Admin to the machines with out having accounts thus fixing the issue with end-users being able to remove IS users.  With the users in the local admin group they can add and remove drivers and software.  I know this sounds like a security problem, but with 9X and ME all the users (by default) have the software.  IF you do not have a Domain, I would configure one of your machines to be a Domain controller this would help you push security polices to all users.  I hope this helps and this should be cost effective as well.  If it does help please don't forget the points.</description>
      <pubDate>Wed, 31 Jul 2002 17:05:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/xp-in-a-95-98-network/m-p/2776724#M1931</guid>
      <dc:creator>John-Thomas Gaietto</dc:creator>
      <dc:date>2002-07-31T17:05:31Z</dc:date>
    </item>
    <item>
      <title>Re: XP in a 95/98 network</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/xp-in-a-95-98-network/m-p/2776725#M1932</link>
      <description>We allow MOST of our users to Admin their own workstations.  As for the others....&lt;BR /&gt;&lt;BR /&gt;We place them in the Power Users group (so they can install software/printers) then restrict access to certain management tools to only the Admin or Admin group.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jon&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Jul 2002 17:43:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/xp-in-a-95-98-network/m-p/2776725#M1932</guid>
      <dc:creator>Jon Finley</dc:creator>
      <dc:date>2002-07-31T17:43:41Z</dc:date>
    </item>
    <item>
      <title>Re: XP in a 95/98 network</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/xp-in-a-95-98-network/m-p/2776726#M1933</link>
      <description>Hi!&lt;BR /&gt; Have you tried making them Admin's of their local(machine name)domain? This resolved the problem that you speek of. On each machine in user manager(not at domain controller) we set them to be administrators of their own machine and it was impossible for them to touch the domain Admin's account because when they logged back on to the doamain they were still local admins but couldn't login as administrator. We also found software that wouldn't install as "Power User".&lt;BR /&gt;Have Fun!&lt;BR /&gt;</description>
      <pubDate>Tue, 20 Aug 2002 09:11:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/xp-in-a-95-98-network/m-p/2776726#M1933</guid>
      <dc:creator>James D. Booe</dc:creator>
      <dc:date>2002-08-20T09:11:10Z</dc:date>
    </item>
  </channel>
</rss>

