Re: Client for M$ Networks, unattended install
- From: "Cary Shultz [A.D. MVP]" <cwshultz@xxxxxxxx>
- Date: Thu, 28 Apr 2005 09:19:26 -0400
I do not think that you need to call someone an a$$hole! Really not
necessary.
There are a lot of people who, when writing 'Microsoft', use the
abbreviation 'MS'. Some people, the original poster included, use the
abbreviation 'M$' instead. Shoot, I have used it myself once or twice. But
always in a good way. I make my living from installing and supporting MS
Software! Well, I used to! Now I am moving in another direction ( web
stuff ).
You would have to ask the original poster whether he/she was trying to be
derogatory with the M$ or not. Simply assuming that he/she was trying to be
derogatory is not a good thing. You know what happens when you ass/u/me,
right?
--
Cary W. Shultz
Roanoke, VA 24012
Microsoft Active Directory MVP
http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com
"Falcon" <Falcon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:47AD2BC2-12BB-4B84-AFAE-F53341B35761@xxxxxxxxxxxxxxxx
> What is M$ networks? Are you being an ass hole?
>
> "PEZ Coach" wrote:
>
>> Anyone point me in the direction of how to script an unattended install
>> of
>> the client for M$ networks?
>> I have 1500 workstations (2K and XP) that will soon need it, and don't
>> really want to manually install on each machine.
>>
>>
>>
.
- References:
- Client for M$ Networks, unattended install
- From: PEZ Coach
- RE: Client for M$ Networks, unattended install
- From: Falcon
- Client for M$ Networks, unattended install
- Prev by Date: Re: Client for M$ Networks, unattended install
- Next by Date: Using sysprep to mimic OEM Windows Welcome
- Previous by thread: Re: Client for M$ Networks, unattended install
- Next by thread: Re: Client for M$ Networks, unattended install
- Index(es):
Relevant Pages
|
|
