PiqueABoo

Q: Can you get this to install the configs from a bunch of existing RDP files?

Someone you recognise from lots of things over the years .. including Dr Who a couple of weeks ago. PS: Although you might not from the "granny" role in The Kumars at No 42.

Would be the only person that does. Don't think you can help it. Nearly did that with some genial minor TV celeb the other month and had what I can only describe as a little battle going on in my head: Sub-concious was firmly trying to make me engage friendly-protocol, conscious was screaming stop and trying to work out why.

A slight tangent. FFDShow has blacklist/whitelist functionality and if an app isn't in either you get some "do you want to.. ?" prompt. I've only ever seen (the target of an MS Remote Assistance session pop that up and would rather it didn't do that. Has anyone been there and sorted this in a prior to deployment package - perhaps by setting it to only use whitelisted apps?

I've encountered that 7-8GB My Docs sync problem - or rather it would sync perfectly, but they kept running out of server quota. Best to ban on what is essentially business equipment, but if you can't then somewhere on the official iTunes site there is a proper guide on how to move it's media library outside of the user's profile.

May or may not help or break something else, but you can change the FQDN it uses in HELO on the properties of the SMTP virtual server -> Select Delivery tab -> Advanced button.

That is the point i.e. your mail server is saying: "HELO animal.ebl.local", whereas in a perfect world it would be, and for this target it needs to be, using a resolvable-anywhere FQDN. Where depends on that missing critical information i.e. what mail server have you got? PS: People that set their MTAs to do that kind of check tend to be irritating pedants. It's just not that useful in the spam wars. PPS: I had to go check this was still the case, but RFCs are not official Internet standards until they're made part of an STD. RFC2821 might be a defacto standard, but out-pendanting-the-pedants it is still a PROPOSED STANDARD for Internet e-mail. [What I'm not sure about is whether the powers-that-be do the RFC -> STD stuff anymore]

I also think it's a copy of the files that were in sysvol on Server2, essentially a backup made before they were replaced by a copy from one of the other DCs. Unless it is really big (why though?) and you don't have disk space, then being paranoid I would leave it alone until you're sure everything is fine and have done a server backup or two. I suppose you have to know what you're doing, but it's not that hard. Think this is more a case of MS wanting to minimise the messes careless people could make when fiddling, so they've left it all sounding a bit arcane and scary.

I'm pretty sure it's been every year.. for starters they "expire" which isn't the right word for a version based licence (one would expect "not valid for this version" or something)..

That would be an Adobe redistribution license ...it feels like you have to renew every couple of weeks... I do wish they'd drop that (or better, Flash would die). FWIW: For several version now, the MSI here is just a simple wrapper around what appears to be the EXE installer you get with the routine download.

I haven't spent any time with Win7 as opposed to 2K8R2 yet but that NonPaged figure of 1460MB definitely looks like the problem. Finding the cause is the tricky bit. PoolMon (which I think you have to get from the Windows Driver Kit for 7.0 ws or svr) can sometimes help a little in that it will tell you which memory tag is responsible, but getting from that to the actually culprit hasn't ever been easy or indeed possible for me... it can be rocket science-ish. NonPaged pool leaks have been rare for me compared to Paged pool leaks. Only time I've seen one it was some dodgy printer monitoring s/w that only ran, and steadily leaked, when someone was logged on.

The share does go away so it can't get used whilst it's being recreated, but should come back automatically and IME it should have all finished now.

I didn't think you were, and what you want is probably sensible.. ..because this (and similar) is arrant nonsense. If you want a network that kinda-works-just then maybe, but if you want a good one e.g. in the same kind of ballpark as CC3 then it takes significantly longer to do from scratch - I reckon it's a minimum of 10 weeks to dot all the 'i's etc.

That explains everything - thought it might be that - and it is not too hard to fix. If you're paranoid then go to Server1 *or* Server3 and make a copy of the good sysvol there (with Explorer to some nearby temp folder). Then do what the event says with that reg value on Server2 - it performs a non-authoritative restore i.e. Server2 will get the latest, greatest sysvol contents from one of the other servers. Do set the reg value to 0 afterwards as instructed.

No relevant errors anywhere..you sure? Next thing I might do if that really is the case is non-authoritative NTFRS recovery on server 2, backing up sysvol and deleting it's contents (*not* the folders) in the middle. Google for NTFRS and JOURNAL WRAP for info on this - the trick is to arrange it so that server 2 will get fresh sysvol contents from one of the two "good" DCs, as opposed to the other way around.

So sysvol isn't replicating to server two. First place to look is in the FRS event logs (on all of the servers) and see what they're complaining about.

::screams again:: ::feels an infinitesimal bit better:: Calling anything "vanilla" is a nonsense in any kind of comparison because they are all different. From that unequivocal position it very easily follows than any assertions about relative difficulty or relative management effort are also a complete crock. You all ought to know better. It is possible to make a DIY system with the same kind of attention to (useful) detail that is better, has far fewer problems, is as easy or easier to manage, than RM's. [Offhand I can think of less than 10 posters on here who judged on cluefulness in arcane areas have almost certainly done that, the rest I'm not sure about.]

I reckon in principle that could also lead to another game to play: corporate defamation. Re. my work I'll just say it's typical pubic sector and let folk fill in the implications however they like. I'm not convinced by that (not least coz of the blind-spot re. the Labour governments).. or is it just that techs are better at perceiving how they're throwing it away?

Another potential outcome is that you eventually get some cash-back from the employer when their smiley-happy rules are held to be unreasonable. On one side we have human rights i.e. freedom of expression in your own life, and on the other organisation's reputation, with a very fuzzy line in between. Obviously it makes for an easier life if you err on the side of caution, but that doesn't equate to blind acceptance of every rule some (proper-advice-free) employer makes up.

Wow... you can just spot the folk who haven't ever spent time tunnelling geeky dos shell commands littered with ampersands and carets through itsy-bitsy-little-holes a mile off! The only niggling doubt I've got is whether WRP might notice you've changed utilman[1], but assuming you've got a cmd shell runnning in local system context **on a domain controller** net user accountname... definitely operates on AD accounts (and if it that weren't the case you could always throw a /domain on the end of the command). [1] In which case there will likely be some other suitable service binary you can temporarily replace that's outside the protective umbrella.

Whatever that means. Did a proper lawyer write that?

::screams:: 1) The terminology really sucks in this thread and I'm pretty sure none of you are running what's usually meant by "Vanilla" i.e. what you get on the installtion CD/DVD with no added extras. What everyone appears to be talking about is: a) Do-It-Yourself (DIY) which has all the config and bits you added b) Off-The-Shelf (OTS) which has all the config and bits someone else added. And of course the OP want opinions on an OTS besides CC4. 2) If a DIY system require significantly more time to manage than a CCx then IT IS NOT A GOOD ONE and/or you're not nearly as clever as you think you are.

Potentially useful (assuming it works). I've used MS Bootvis for this in the past, but that stopped working for me quite a while back... and yup, procmon through a boot & login does my head in too.

Nope - I reckon it's home user technology well out of place in this kind of scenario. [Will be interesting to see who thinks otherwise now ]

::you just know what I'm going to say, don't you?:: On the tin MS say: "Note that this encoding only prevents casual viewing of your code; it will not prevent the determined hacker from seeing what you've done and how". I can be a seriously determined hacker if required, but didn't have to do anything hard/determined to subsequently decode the vbe here. Well unless a quick google for a decoder counts.