Orangutech's questions

This particular environment, it's VMWare guests that have been moved to all-flash SAN, but that shouldn't be particularly relevant.

I'm quite familiar with >winsat formal from SO questions like this one to get Windows to re-test the OS disk. However:

1. Windows (Server, 2016) only recognizes the change on the OS drive.>winsat disk -drive d (as example) runs the tests, but Defrag/Optimize util still sees all non-OS drives as HDD, and will happily defrag them.

2. I haven't yet been able to get even winsat diskformal to properly run and "take" over Remote Powershell Sessions. (It appears to run fine via invoke-command, but Defrag will still see it as HDD, unlike running it via RDP session.)

In the meantime, I've disabled the auto-defrag task on all the servers (probably should have been off already.)

So my questions are:

1. Does anyone know of a method other than winsat to make Windows re-evaluate it's attached drives? (Or a way to make winsat accept/care about the values of non-OS drives.

2. Has anyone gotten even "winsat formal" to run correctly via invoke-command?

3. Other than wasting electrons and write-cycles, does Server 2016 do anything differently with disks detected as SSD vs HDD besides allowing defrag, when TRIM is not available. (Being a SAN, it's not.)

I'm stuck. I'd like to think I'm reasonably good looking info up, but for the life of me I can't figure out how to deploy mac software in an enterprise, like with Group Policy.) I'm not talking about deploying images, I mean, for example how to make sure every mac has the latest version of flash installed, or whatever. (I'm not expecting to support third-party installers, just .pkg and maybe manual "Put this directory here", which of course I can roll my own .pkg for.)

I've got an OSX server (10.6) setup in "Golden Triangle" (OD talking with AD) so users can log in with their AD accounts, and I can manage Apple updates, or user preferences, but deploying...? Am I missing something obvious? (Or is it Apple?)

P.S. We have Apple Remote Desktop as well, but that's only for one-off's...

Goal: Have 389DirectoryServer (AKA Redhat/Centos/Fedora DS) pull account info from AD, allowing both AD accounts and 389-native accounts be authenticated through 389DS, but have the sync be one way, AD->389. We don't want accidental/malicious changes made on the 389 server to replicate back to AD. Ideally, we also wouldn't have to have use a DomainAdmin equivalent user.

All the existing documentation (most referencing http://www.centos.org/docs/5/html/CDS/ag/8.0/Windows_Sync-Configuring_Windows_Sync.html) makes it appear to be a two-way sync. Am I barking up the wrong tree?

**Edit:**I was going to not explain the higher-level goal in order to keep it focused, the actual endgame is for our students (to be provisioned in 389) and our employees (in AD) to be able to authenticate against CAS for our various systems, mostly web-based.(http://www.jasig.org/cas). Don't ask why we're doing it that way, that's just what was presented to me to support. I have a feeling there's a simpler/more obvious/more commonly documented way, but I"m certainly not a cross-platform authentication/authorization expert. (Words like kerberos, RADIUS and/or PAM come to mind, but I don't rightly know exactly what all those actually are, the pros/cons, etc...but since we're already using RADIUS against our AD for Wireless 802.1x...)

Short version: Is there a way to have Exchange route all email, including internal AD users that would normally be routed directly, through an external gateway? (SMTP, probably a "Smart Host" in exchange nomenclature.)

Longer version: I'm not an email expert/admin/orevencompetent. Inherited an exchange 2003 server, migrating to web-based SaaS provider. To add to the fun, we're also (forced by deadlines) transitioning domains. What we (my boss) wants is any email sent to the new domain to have a copy sent to both domains. Getting mail sent to the new domain/provider to then be copied/forwarded to our old domain/exchange is easy. But we want mail sent from the old domain to the old domain to get sent to the new domain as well.

However: If we route all outgoing exchange mail through the new provider gateway, w/ the new domain forwarding to the old, we'd get an email loop. The "solution" desired is for an exchange user that sends to another exchange user to still be sent via the external gateway, which would in turn be sent to the new domain, and copied/forwarded back to the old domain. Is it possible?

A bit of a strange request I'm sure. And I expect that what we're attempting to do is DoingItWrong(tm). Any better ideas?