chrisbrown

mrbios - I was on a fairly strict budget and the UD4 seemed to present the best bang for my buck. And the disk performance is perfectly acceptable...I'm not *overly* concerned about how this thing scores. Manages CS:Source that I play at 300fps.

My new PC i7 2600 (3.4GHz, 4 cores) GA-P67A-UD4 6GB RAM 1TB 7200rpm Samsung ATi HD6870 http://i55.tinypic.com/33wbfnm.png

Hi deano, I've not had this problem myself, but for a lot of OWA/ECP/OA errors the easiest and most reliable solution is just to nuke the virtual directory and start again. Be sure to take a note of relevant settings then do the following: Get-OwaVirtualDirectory | Remove-OwaVirtualDirectory New-OwaVirtualDirectory Then return and configure as necessary. I know this is a drastic measure but you'll often find it fixes most issues with OWA/ECP/OA. Hope this helps, Chris

Without trying to sound condescending, I'd really suggest you head along to an Exchange course. I did 10135A in the middle of a 2010 deployment and it completely changed my mentality on the matter. There's all sorts of things that TechNet covers but doesn't quite explain the importance of that you can learn in the course. It also has a heavy reliance on PowerShell which TechNet doesn't enforce overly well. If you can find the time/money to go, I consider it a very worthwhile investment.

If you're feeling lazy enough, here's a simple PowerShell script we use here. Still in development - need to allow it to drop a ping or two before emailing (it's a little premature), but works well for our needs. Will monitor any device that can respond to pings. Firstly, edit the variables up top in Invoke-PingStats.ps1 To add a host to be monitored, run .\Add-Host.ps1 -hostname optionally you can add -configfile and/or -ip parameters. eg. .\Add-Host.ps1 Google (will look up via DNS for IP) or .\Add-Host.ps1 -hostname google-public-dns-a.google.com -ip 8.8.8.8 To begin, simply run .\invoke-pingstats.ps1. PingStats.zip

You're a funny man. This is a joke, right?

Tooheys Extra Dry and XXXX are where it's at ;-) Also, I'll support Green and Gold to the grave, but my money's on the Poms this year.

Well aren't you just a little ray of polite sunshine flowing into my Saturday morning. Abaddon is right, I was referring to your using forward slashes instead of backslashes. If you have accounts with the same username and password on both machines, and they are local administrators, they will both have full and unrestricted access to each other remotely.

I would...but I'll be home in QLD for the Christmas break...And I'm not so keen on VB, tastes like gutter water mixed with fresh manure if you ask me

nagios can do EVERYTHING. You can even attach it to temperature sensors and integrate with mrtg. This will give you graphs of your server room temperature and alerts when over a specified threshold. Easy as to configure too.

I've been at the pub for too long to answer your question correctly, but I will say it's not Microsoft's problem. Also, if you want to browse, use a UNC path...ergo \\x.x.x.x\share also, best to use the exact same set of credentials on both machines, this will allow for easy sharing. As in...create the same account on both machines as a local admin.

I don't even like the sport...but sigh.

and so begins another day... May the best Aussies win.

If it absolutely must happen on first logon, you could always trigger a script running xcacls or Set-Acl or similar...That said, AngryTechnician is probably on the money, two refreshes for definite. Obviously in some instances two refreshes may not be suitable, in which case a script can provide you some element of a guarantee.

Is the 2003 box a file server? Do you have scripts/GPOs telling your machines to map to \\contoso.com\FileShare? When you dcpromo a member server, it adds to the A record for your domain (and a bunch of srv records to) the details for the server. For instance, currently you have something like this: DC2k3 (Server 2003). Your A record for contoso.com contains one entry only; DC2k3. Anybody pinging or doing an nslookup against your internal DNS looking for contoso.com is being returned the IP of DC2k3. When you introduce DC2k8 to the scenario, another A record is added for contoso.com (thus enabling round robin). When a user requests contoso.com, the DNS will give back either one of the two servers' IP addresses. If you have drives mapped to the domain name and haven't used DFS to handle it, you will run into issues. Can you confirm that the drives are mapped to different servers? Also, do a "dcdiag /c /q /s:DC2k3" and "dcdiag /c /q /s:DC2k8" against each DC (obviously you'll need to re-dcpromo 2k8 at some point to do so). This will tell of any critical errors that may be occurring. Chris

Wasn't meant to be snide, I was just putting it there for information's sake. Perhaps someone browsing may find the information useful.

From memory, the following are containers, not OUs. I've probably missed some though Builtin, Computers, System, Users, LostAndFound, Microsoft Exchange System Objects, Managed Service Accounts.. I think there's more to do with NTDS and such, but I can't recall them right now.

Assuming you host your website internally, or at least host some sort of http:// site that is accessible inside and out, just put your proxy.pac on there. We host our website in our DMZ, and have the network set up so you don't need to be using the proxy to get to it. That way no matter whether the notebook is on campus or at home, it can access the proxy.pac file and know exactly what to do. For example: function FindProxyForURL(url, host) { if (isPlainHostName(host) || isInNet(host, "123.123.123.0", "255.255.255.0") || isInNet(host, "192.168.211.0", "255.255.255.0") || isInNet(host, "172.17.0.0", "255.255.0.0") || isInNet(host, "172.18.0.0", "255.255.0.0") || dnsDomainIs(host, ".yourschool.edu")) return "DIRECT"; if (isInNet(myIpAddress(), "172.16.0.0", "255.255.0.0") || isInNet(myIpAddress(), "172.17.0.0", "255.255.0.0") || isInNet(myIpAddress(), "172.18.0.0", "255.255.0.0") || isInNet(myIpAddress(), "172.20.0.0", "255.255.252.0") || isInNet(myIpAddress(), "172.24.0.0", "255.255.252.0") || isInNet(myIpAddress(), "172.31.0.0", "255.255.0.0") || isInNet(myIpAddress(), "10.10.0.0", "255.255.248.0") || isInNet(myIpAddress(), "10.10.8.0", "255.255.252.0") || isInNet(myIpAddress(), "10.20.0.0", "255.255.252.0") || isInNet(myIpAddress(), "10.20.4.0", "255.255.252.0") || isInNet(myIpAddress(), "10.22.0.0", "255.255.255.0") || isInNet(myIpAddress(), "10.21.0.0", "255.255.255.0") || isInNet(myIpAddress(), "10.24.0.0", "255.255.224.0") || isInNet(myIpAddress(), "10.24.60.0", "255.255.255.0") || isInNet(myIpAddress(), "10.24.61.0", "255.255.255.0") || isInNet(myIpAddress(), "10.24.62.0", "255.255.255.0") || isInNet(myIpAddress(), "10.25.0.0", "255.255.252.0") || isInNet(myIpAddress(), "10.50.0.0", "255.255.224.0") || isInNet(myIpAddress(), "10.51.0.0", "255.255.224.0") || isInNet(myIpAddress(), "10.52.0.0", "255.255.224.0") || isInNet(myIpAddress(), "192.168.212.0", "255.255.255.0") || isInNet(myIpAddress(), "192.168.192.0", "255.255.255.0")) return "PROXY 123.123.123.123:80"; return "DIRECT"; }

At home, I'm all for dumb names, but in the office, I need to know exactly what any box does at any particular time. When I worked for an international company we followed this convention (detail [number of characters]): country[2]region[3]purpose[2]site[2]number[2] i.e. in our head office, the third SQL server was called AUQLDHOSQ03. In the data centre, the 17th Citrix server was called AUQLDDCCT17 etc etc. In the school I'm in now we use campus[2]-physical/virtual[1]-purpose[]number[2] for example SY-V-MG01 for the management server, GW-P-DC01 for a DC at another site.. SY-V-IIS01, etc etc. I'm not a fan of dashes as they make typing and saying a name of a server difficult. For example ess why dash v dash eye eye ess zero three is harder than ess why vee eye eye ess zero three...If that makes sense...I'm a bit anal retentive about server names..They have to match convention perfectly or they get renamed as far as I'm concerned. When you manage 60 or more servers, name guessing needs to be done, so if you're not sure of the convention used it gets even harder. Imagine trying to remember 60 different cartoon characters and what each server does! That said..our DMZ servers all have star wars names. There's only 8 servers in the DMZ so it's not such a big hassle. Edit: Forgot my home names! Media Server: tihSevreS (read backwards..will make more sense) EeePC: Eeeee Mac Mini: inimac NAS: Bruce Parents PC at their place: xyz

Thanks heaps! Immensely so. I didn't get any significant pay rise coming here, but tonight is my first night of doing work after hours, and all I'm doing is sitting and waiting for a bash script to run over our mail proxy. Once it finishes, I make sure it was successful then run another script...It's a tough life. It's a nice breath of fresh air after working 50+ hour weeks for the last 6 months. Not being on call any more is nice too...

"Just because you can doesn't mean you should" is something that I think rings very true here. Your print server is under enough load simply to account for print jobs, letalone scan every single one of them for coverage. If you've only got a thousand or so jobs in a day and a dedicated print server this may be suitable. We have a dedicated print server, with hundreds of jobs in the queues at any one point and I know for a fact that implementing any extra processing will kill the poor box - and it's a Xeon 5500 with 12GB of RAM! Papercut will do that to you ...

This is the setting I was thinking of...Hopefully this helps with sorting your issue... http://i53.tinypic.com/21l6a7n.png

SuperBump! I've just come from being a Systems Administrator in a publicly-listed international accommodation company based in QLD, and am now working as an AD/Messaging Admin in Melbourne at one of Australia's biggest private schools. My interests lie mostly in Exchange/SQL, AD is getting a bit *yawn* after 4 years of doing it. I'm mid-way through an Exchange 2010 deployment at the moment which I'm loving, and have many many things planned. I don't know any other school IT staff (other than those I work with) so I guess I'm here to get a bit of a distributed view on things... Our department supports approximately 1400 notebooks and about 300 desktops (PC+Mac).

I'm at home and about to go to bed, but WSUS has an option to use it just for cataloguing and approving updates. When this is enabled, workstations will still download their updates from the internet whilst reporting back to your WSUS box. Perhaps check this? It's in options somewhere. You only need to configure it on your top-most server, replica servers will pull this down.

shutdown.exe doesn't allow for cancelling without running "shutdown.exe -a" which obviously most people cannot (command prompt is likely disabled, and the user probably couldn't work out how to run it anyway). There's a million free programs out there which will give you the option, I'm with the psshutdown recommendation. You *do* have PSTools installed on your management server, right?