Re: Mac pc connected to Windows 2003 std server
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Wed, 12 Jul 2006 00:39:28 -0400
In news:uDfm4nDpGHA.5104@xxxxxxxxxxxxxxxxxxxx,
Robert L [MS-MVP] <noreply@xxxxxxxxxxx> stated, which I commented on below:
Hi Ace,
Thank you for the input.
No problem, Bob. I thought to offer that tidbit about Quark and other apps.
I've seen it a few times and it becomes a pain to deal with especially if
the users don't *feel* like actually specifying the extension name. I've
talked to numerous Mac users who blantanly trash Windows because they don't
feel like it should be necessary for them to do this. I explain that it is a
Mac limitation, not a Windows limitation, on the way Macs handle file types.
If only Macs just keep the file streams in one file and not splitting it
into two, whether the extension is provided or not, would make life easier
for all. After all, Windows does it!
There are other issues that bug me about Macs in a mixed environment,
especially AD. For one, the UnixID that they *recommend* but they use a
non-RFC attribute (which conflicts with the real one), which I think is
useless because all we have to do is kerberize an OSX and bind it to AD.
OTherwise, their recommendations with this useless attribute causes numerous
issues when upgrading to AD 2003.
I hope everything is going well for you Bob!
Ace
.
- References:
- Mac pc connected to Windows 2003 std server
- From: Scott
- Re: Mac pc connected to Windows 2003 std server
- From: Ace Fekay [MVP]
- Re: Mac pc connected to Windows 2003 std server
- From: Robert L [MS-MVP]
- Mac pc connected to Windows 2003 std server
- Prev by Date: Re: Features in Windows 2003 DHCP
- Next by Date: Re: Site without DC
- Previous by thread: Re: Mac pc connected to Windows 2003 std server
- Next by thread: should nslookup resolve by using single-labels
- Index(es):
Relevant Pages
|