She's talking about Exchange 2007. Go look at the ms Exchange blog site and you'll see some references. (http://msexchangeteam.com/default.aspx)The nice thing about it is that most everything that I saw that they were doing with a command line you could do with the GUI. The only difference is that
Yeah that doc is supposed to be about what they are doing with MONAD for
Exchange. I, for one, based on some EHLO blog posts am concerned about its
functionality and how it will work in large environments. I will try to
download and read that doc to see if it has any meat in it but most Exchange
I have found that trying to surf with servers doesn't work really well, the
buoyancy factor is not substantial enough and as you paddle out to catch the
big one you tend to sink before you get there. Actually having your ankle
tied to the server makes for a rough day for yourself too.
Actually
I would tend to agree with Al on this point. I haven't seen
a need for teaming and feel that the more complex device drivers could actually
put you in a position of failure and watch out for the times where someone
accidently misconfigures something and you start getting really odd
Actually, you've got that a bit
backwards.
The Exchange GUI for 2007 is built completely on
Monad/PowersHell cmdlets. In more recent builds, the GUI displays the cmdlet it
executes to help the admin (if he/she so chooses) to learn the scripting. I
don't think those builds are generally
In larger companies browsing really isn't used all that
much as there are quite a few things that can screw it up. It is entirely a
broadcast based mechanism and I have seen several companies just start disabling
the browsing service altogether to help alleviate browe master wars, etc. On
ROFL
Brilliant.
--
O'Reilly Active Directory Third Edition - http://www.joeware.net/win/ad3e.htm
Do not read this worthless blog entry on Defending Security Infrastructures -
http://blog.joeware.net/2006/07/11/445/ --- I'm serious, you will learn
absolutely nothing about Defending
The second is to publish resources in Active Directory. This is
fairly common for printers though more and more I seem to be seeing people just
sticking a sign up on local printers with the queue name and DNS name to avoid
someone moron from accidently picking a printer somewhere he
Title: Home directories issue
Has any headway been made with this problem?
I cant find any solutions out there.
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Conrad, Daniel C Mr. Nortel
PEC Solutions
Sent: Tuesday, December 13, 2005
3:17 PM
To:
With
the Print Management Consolethat was introduced with Win2K3 R2, managing
printers is *significantly* easier and ACLing them appropriately becomes a more
realistic task. It's also now downloadable separately from R2 and will run on
Win2K3 SP1+.
Hey
all,
Does
anyone have any comments/articles, etc on the benefits or concerns of a clean
install of Windows 2003 Server VS an Upgrade? My opinion is that doing a
clean install keeps system root clean. It also pristinely adopts the
security best practices of 2003 Server. Disk
Personally I hate OS upgrades and try hard to avoid them and prefer to choose a
fresh clean install...
Although supported when upgrading an OS old stuff from the previous OS is kept
and besides that you might run into issues because of incompatibilities with
software, drivers, etc. A clean
I'll be really interested to know if the underlying protocol for talking to
Exchange remotely is any different than webdav in the next release. I admit
to not having looked at the Power Shell stuff for Exchange yet, so I have no
idea. I kind of hate programming Exchange, so I tend to avoid
I've heard there's ASP.Net webservices that expose a lot of this stuff.
Thanks,
Brian Desmond
[EMAIL PROTECTED]
c - 312.731.3132
-Original Message-
From: [EMAIL PROTECTED] [mailto:ActiveDir-
[EMAIL PROTECTED] On Behalf Of Joe Kaplan
Sent: Sunday, July 16, 2006 2:57 PM
To:
There are a few times where upgrading is easier than installing fresh and doesn't have that big of an impact... but most times I prefer to simply install fresh.There are only a few examples of where I think that upgrading is better or easier overall:
1) Workstations -- I'd rather upgrade a Win2k
Well, when you're mapping to \\server\share\directory, if the user has permission issues at the directory level (their actual home share location), I believe that it will simply map to the share and not go into the directory.
Make sure that you have granted all users Full Control at the share
Taking everything you said, why would this
problem be intermittent and not every single time the user logs in?
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Hargraves
Sent: Sunday, July 16, 2006 6:03 PM
To: ActiveDir@mail.activedir.org
Subject: Re:
I agree with Jorge on this. Every new OS MSFT comes out with they tell you
that it is much better at handling upgrades than the last and how bad the
last one actually did it. So if someone tells me K3 does it great I tell
them to say that when say LongHorn comes out. :)
Anyway, you will have
The plot thickens. I'd assume that PS and ASP.NET are using the same
network layer to do the actual heavy lifting, so the question is then, what
is that based on? :)
Joe K.
- Original Message -
From: Brian Desmond [EMAIL PROTECTED]
To: ActiveDir@mail.activedir.org
Sent: Sunday,
The statement that with each new OS the upgrade in place scenario has
improved, at least to date, has been true. If they said it's perfected each
time then I could see your point. I've been to many customers that have
done in-place upgrades of the OS with great success. Is it the preferred
I would like to point out though that a inplace install machine leaves
behind a mixture of 2000 and 2k3 permissions an d thus a comparison to a
true Win2k3 box is sometimes a bit tricky.
Combined with that the SFN issue...
http://support.microsoft.com/kb/195144/EN-US/
Us SBSers are facing the
Oh I'm definitely not saying it isn't getting better. It truly is. But with
each release they tell you it is great and go ahead and do it and then the
next rev is when they tell you all the things that were done wrong that they
now do fine. While they don't tell you it is perfect, you certainly
Drifting OT... I find myself often following behind those perfect world
folks, having to break the news that their wonderful product (I've seen no
monopoly by Microsoft (no pun intended); this seems an equal opportunity
offense by sales folks and certain types of consultants of all vendors). I
23 matches
Mail list logo
