tarquel

I suppose it also depends on what the site itself is doing.... How about ticking Exchange Users on the last tab.

ptotham... did u look at the article ive stickied on this forum board? Gives you a full outline on what to setup for Win7 and some good, established best practices for doing so etc... also: you could do this by seperating them out using OU's or via WMI filtering i recon. If the different types of user always use the same machines i.e. teacher only uses teacher computer, pupil only uses pupil computer, you could assign the GPO's by Computer type OU and do it this way. I would STRONGLY suggest having a seperate set of GPO's for win7 use, as mixing them up between Win Vista/7 and XP can produce all sorts of weirdness. Naturally, GPO's for Office 200x settings and that sort of thing can apply to both, but for OS specific stuff, its best (in my experience) to keep them seperate, and use Replace methodology where possibe. EDIT: whoopsy, didnt notice the mandatory bit... Steve's info looks sound, but do look at that stickied article too, as it will help with some of the other stuff etc Cheers.

Have you checked on that Recieve Connector the Authentication and Permission Groups tab? What do you have there? Have you tried only selecting Externally Secured under Authentication (or possibly Intergrated Windows Authentication) and under Permission Groups, try ticking Anonymous as a test: EDIT: Beat me to it by one minute Techieshelp

Just to get more info.... How are you deploying this as part of the OSD TS? via Collection Variables or via Install Software install in your TS? (or some other way) Are you running SCCM Natively or in Mixed Mode? Quite the puzzler tho... Also, is your DP the same or different server as your site server? Is BITS and associated services running correctly? I seem to recall that after a recent update - possibly R3 or some hotfixes - while everything was working correctly as far as current packages went, when i went to update them, things werent working as expected, for no apparent reason. Cant remember exactly what it was offhand, but I did have to remove the BITS Server Extensions (in the 2008 Features list) from the DP server (or might have been site server), reboot, install it again, reboot, and help / poke SCCM's services until things were working again. I did read that rarely, this can fail for no reason and something like the above is the cure, but take with a pinch of salt Nath

Yes. a user logging into OWA constitutes a user CAL being needed for that user. I believe that you can actually get Exchange User CALs specifically for External Use, so that you could buy the required amount required for the users accessing from external. I also beleive the amount of CALs required isn't a concurrent use one, so you couldnt just get 80 of them and cite that only 80 of them wud ever connect at one time - its one CAL per AD username as i understand it. Havent got a chance at the moment to check my license sheet, but i can give u the specific MS product code if needed, although it'd probably be for Exch 2010, and again, without checking, I dont know whether they are backwards compatible (i'd assume Exch CALs might not be without checking that too). Cheers

Did u actually check that the directory on the DP(s) had gone? i.e. not just go by what SCCM was telling you. Have you queried the logs to see more detail on why its failing? either directly by using the F8 command line within the boot image [assuming u have enabled that] or by looking at the logs via the Advertisement of the OSD TS. Cheers

purely from memory, i think u give the root setup exe a /admin parameter from the command line (a bit like office 2007 onwards).

You've run through the Configure Wizard of the WDS server right?

I havent personally got it to "look up" its own name when deploying via MDT/SCCM but certainly sounds good if its possible. I know that if you script the joining using the Task Sequence, it will auto use the same computer object in AD etc i.e. no duplicates, at least, it works for us What I'm aiming to do is to use the Asset Tag [NOT Service Tag] of a machine (we use Dell) and have that populate the computer name automatically. Currently, it isnt used so I'd have it go something like this: - Pre selection of Task Sequence, check the asset tag and replace the computername variable with this - If correct, then the techie performing the deployment doesnt need to alter it, but if it hasnt been set yet, then they can correct this to what it should be - During the Task Sequence deployment of the OS, it writes back the chosen computername into the BIOS of that machine (so its set for a future time) Unfortunately, Dell's tool isnt the easiest (i.e. seems in some way to have to be installed / added to the Boot Image) so I cant just roll out a update to all machines with a script that auto places their computername into the BIOS of their machine At least.... I dont *think* i can Anyhow, thats just an example of what I'm aiming to do, and as I say, when the Task Sequence joins the machine to the domain, and uses this computername, if it already exists, that object is used so theres no error or duplicate errors (at least I havent seen any), which isnt like RIS that would [rightly] moan if you were trying to add a computer that already exists in AD. MDT seems to handle it better, or at least, SCCM with MDT does at any rate.

You can configure Task Sequence variables in the Task Sequence to do this. Lets put it another way, how do YOU want it to name the computers? The MININT thing is because its being executed from PXE and thus treating it as a bare metal install. While I'm only really on the angle of SCCM with MDT OS deployment, i believe alot of it is the same - as far as the Task Sequences go - so tell me how you want to name them first i.e. do u want it to auto take the Asset Tag or Service Tag [if Dell], do you want it so you can type the name in yourself, etc etc? Cheers

does the ExBPA tool health check diag give u any clues?

Have you updated the NIC / Storage drivers at all to cater for these new machines? Even if its the same chipset(s) as a previous model, it still may require a newer version of the drivers bear in mind

See if you can find any detail in the actual logs: C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\ You may have an additional folder in there or something. I've not yet attempted to set this up yet, being that we have quite a few levels of spam/av protection before the emails even reach Exchange hehe but i will do at some point. Nath.

It sure can And yes, you can integrate MDT into SCCM i.e. use the power of MDT in your SCCM Task Sequences

I'd suggest running through that MS tool i mentioned in my first reply, to see if that can shed any light on whats best to do. Sukh would be able to suggest more as he's likely done it. Cheers

Hi Joe. Make sure you're running MDT 2010 Update 1 first of all: Download details: Microsoft Deployment Toolkit (MDT) 2010 Update 1 Additionally, download and look at the documents in that print ready zip specifically the Quick Start Guides (minus the SCCM one hehe) I found it pretty invaluable initally, although I was following the SCCM one, there should be plenty in that document pack to sift through. Providing you have WDS / DHCP etc all set up, you can find some guides in the stickied thread here: [ http://www.edugeek.net/forums/o-s-deployment/56928-complete-guide.html ] or check the forums here: [ http://www.windows-noob.com ] for bits n' bobs I'm planning to write up something myself soon regarding both MDT deployments and SCCM deployments so er....watch this space

I believe he's refering to the AD group "Exchange Servers" that should be in the OU "Microsoft Exchange Security Groups" (located at the root of your AD), i.e. these:

what format do u use? In the EMC, go to Org Configuration > Hub Transport > E-Mail Address Policies In there, you can create one (i left the default one, and made a new specific one for the job - i.e. Users with Exchange mailbox > First.Last name for exchange mailboxes in our case.

Never needed to do this myself [yet] but we just use Group Policy to populate machines with Wifi Connection settings Of course, if your not on a domain, then thats no help at all and ill just shut it Nath

I would if you have volume licensing. It's not too complex and plus if your deployment testing needs to span some time, its easier on yourself if you have this up and running initially to not have activation problems adding to the issues. Most likely, depending on how your gonna set up your chosen deployment system. Pretty much, although again, it depends how you want to play it i.e. whether you build up a image, sysprep and capture it, and then deploy it out, or whether you just deploy everything using Task Sequences in MDT with WDS (think of it like a unattended CD with scripts to install and tweak as it goes along), or, and this is kinda of what I do, use a TS to create and capture the image, then use another TS to deploy it as appropriate.

Does the Exchange Server Deployment Assistant tool (Exchange Server 2010: Exchange 2010 SP1 Help) give u any help with that? I'm afraid I havent gone from one version of Exchange to another so I've not really looked into how it works, but this tool might help a bit perhaps (if you havent seen it already). Cheers

(thats what i meant )

From the Event Viewer, can you post the full info it gives you when locking up?

Just a wild thought but whats the OS of the server itself? What A/V are you running on it? Has that updated more than its definations recently? We found a weird one with NOD32 v4 [i think it was] on a Server 2008 R2 file store, and couldnt understand why the performance of clients using it for roaming profiles / offline files were having such sluggish behaviour. Discovered it was (partly) down to NOD32 v4 on it... removed that and it flew again Its just a wild stab in the dark incase you've inadvertly installed / updated some AV product and overlooked that bit, especially those that mildly hook into the network adaptor too Cheers

Indeed.... I've been there and got that T-Shirt ...to help them with this issue: The Exchange Mailbox Replication service crashes when you use the "New-MailboxImportRequest" command to import a PST file to an Exchange Server 2010 mailbox (i.e. importing PST's was a royal pain in 2010 SP1 over RTM....specific service crashing a plenty so gotta say that we, and probably a few other org's, helped get this much improved in U2....tho the recent U3 appears to mention it again, so maybe they've further improved it again ....but we digress )