Re: How To Abandon Microsoft

From: Andrew Swallow (am.swallow_at_btopenworld.com)
Date: 09/26/05 

Date: Mon, 26 Sep 2005 17:30:17 +0000 (UTC)

tomstdenis@gmail.com wrote:

> Mxsmanic wrote:
>
>>Hugo writes:
>>
>>
>>>Just wait untill you have a few hours without much of a workload, and give
>>>the instruction; no exactly hard ...
>>
>>Sounds like you've never had 40,000 desktops to upgrade worldwide.
>
>
> If you have 40,000 desktops that must all be live and mission
> critical... then you have a lot of thinking about past mistakes.
>
> If they're just say, oh I don't know, work stations then you upgrade
> one department at a time. Keep cross-platform tools up e.g. samba
> shares for instance and go on your way.
>
>
>>Upgrades can take many months in production environments.
>
>
> Because you don't have enough staff. That's like saying it could take
> a month to clean an entire 60,000 sq.ft complex ... if you only have
> one janitor.
>
>
>>>You must run a LOT of old out of date software then.
>>
>>No. I just have actual experience running large and small computer
>>systems and networks in real production environments.
>
>
> Running windows? Yeah no wonders you're so negative.
>
>
>>>I work in the the telecommunications / carrier industry, in our industry
>>>upgrade is essential for production environments.
>>
>>Upgrades are essential at some point in every production environment.
>>But you do not perform them if they are not essential, and you spend a
>>tremendous amount of time testing them and rolling them out when they
>>are. Telecommunications is a special flavor of production
>>environment, so the rules are slightly different in the details, but
>>the same principle applies.
>
>
> Granted and agreed. You don't need to update boxes for trivial fixes.
> Though a careful [clonable] design lets you get away with quite a bit.
>
>
>>>But what sort of person would run a single user operating system in a
>>>network environment?
>>
>>A single-user OS makes sense on the desktop, even in a network
>>environment.
>
>
> Spoken like a true Windows pre-NT advocate.
>
> single-user does NOT make sense. Think "user" + "root".
>
>
>>>In Microsoft systems a end user can change the operating system itself,
>>>just load some program or virus and suddenly the machine is destroying
>>>data or some such nonsense ...
>>
>>Not when the machine is locked down. NT-based operating systems can
>>be tightly secured.
>
>
> And this is through ... MULTIPLE USERS.

No through User *ACCOUNTS*.

Users are apes with two arms. Most modern computers only have one user.

An administrator account that allows the loading of software and a
network administrator account that allows a centralised administrator to
remotely upgrade the computer are very useful.

Note home users need the ability to load games from normal accounts.

Andrew Swallow

Relevant Pages

  • Re: How To Abandon Microsoft
    ... Sounds like you've never had 40,000 desktops to upgrade worldwide. ... Upgrades can take many months in production environments. ... A single-user OS makes sense on the desktop, even in a network ...
    (sci.crypt)
  • Re: Local Security Policies
    ... This small VB Script will make the registry change necessary for the Administrator account to be available on the Welcome Screen. ... There is a space between Windows and NT in the above Key. ... I am having problems with> the Local Security Policy options after an upgrade. ... I found that> several options in the Local Security Policy / Security Options were> desensitized and they could not be set. ...
    (microsoft.public.windowsxp.security_admin)
  • HELP! XP Pro install set random passwords
    ... >I did an upgrade from an OEM XP Home Edition. ... >the XP Pro upgrade and did the install. ... >screen comes up w/an administrator account and my name ...
    (microsoft.public.windowsxp.security_admin)
  • I forgot my administrator account password
    ... administrator account. ... her printer needs to be on a usb driver ... or help me create a reformat disk ... I have also lost my upgrade disk and info. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Cant Log in after Upgrade to 2000 from 98?
    ... I am not sure how that account would be configured in a W98 upgrade. ... reset the built in administrator account. ... > I've finished with the software install and removed it from the domain and ... > of for and Administrator User but nothing seems to work.. ...
    (microsoft.public.win2000.setup_upgrade)