3,165 reputation
52675
bio website lamontconsulting.com
location New York, NY
age 37
visits member for 3 years, 11 months
seen 2 hours ago

SSL isn't good enough. Your website can be hacked.
Help solve the problem by advocating these RFCs:

TLSA (formerly DANE for DNS) Fixes the hackable CA problem

TLS-OBC: Fixes TLS, and the Related Domain Cookie Attack


About me
I have no relation to the above sites; I am just an advocate

Why "makerofthings7"? It's a challenge to "make seven things in my life of significant quality and value". Who knows if those things will take the form of software, art, or people. (I'm not married, no kids yet)

See ...my LinkedIn profile


Jul
8
comment Can a single ADCS instance “hold” more than one PKI namespace?
I added detail on why I think it's a good idea to consolidate instances... namely the 2nd tier will scale out horizontally with 10,000 + nodes.
Jul
8
revised Can a single ADCS instance “hold” more than one PKI namespace?
added 140 characters in body
Jul
8
comment Can a single ADCS instance “hold” more than one PKI namespace?
I got rid of the wording PKI hierarchy and clarified that I'm focused on consolidating policy servers. In my case I'm allowing each customer (of which I have 10,000 - 50,000) to generate their own certificates, given the constraints existing in the policy server (EKU/Name constraints)
Jul
8
revised Can a single ADCS instance “hold” more than one PKI namespace?
added 401 characters in body
Jul
7
awarded  Cleanup
Jul
7
revised How do I import into ADAM / AD LDS - The specified instance type is invalid
rolled back to a previous revision
Jul
7
revised How do I import into ADAM / AD LDS - The specified instance type is invalid
deleted 78 characters in body
Jul
7
answered How do I import into ADAM / AD LDS - The specified instance type is invalid
Jul
7
awarded  Promoter
Jul
7
accepted I have Windows servers in the cloud. How can I tell if WSUS will help me save money?
Jul
7
accepted Possible to make SMIME signatures not appear as an attachment? (e.g. in Gmail)
Jul
7
comment MPLS outage on a 4 member DAG causes Exchange / Outlook to hang
@mfinni - Checked the logs, nothing found... did see local connectivity issues, as mentioned above... perhaps it's a local switch issue
Jul
7
revised MPLS outage on a 4 member DAG causes Exchange / Outlook to hang
added 921 characters in body
Jul
7
revised MPLS outage on a 4 member DAG causes Exchange / Outlook to hang
added 253 characters in body
Jul
7
asked MPLS outage on a 4 member DAG causes Exchange / Outlook to hang
Jul
7
accepted What is the correct way to track and monitor Exchange DB replication “pressure” over time?
Jul
7
comment What is the correct way to track and monitor Exchange DB replication “pressure” over time?
Yes, it seems that @MDMarras logic would be correct, I have 5 databases / logs on the same lun. Rather than graphing the log files per hour it makes more sense to generally identify the heavy hitters in that DB set in general, and move them. I'll be parsing logs soon. Thanks both!
Jul
7
comment What is the correct way to track and monitor Exchange DB replication “pressure” over time?
@TheCleaner The WAN bandwidth constraint is preventing the timely truncation of logs (I think logs are only truncated when a full backup occurs and the data has been replicated to each DAG member). It eventually does catch up, but not often enough for us to get scarily close to filling the drive. I think that by moving active mailboxes to other LUNs, the replication issue will still exist, however the disk space issue will be temporarily relieved.
Jul
7
comment What is the correct way to track and monitor Exchange DB replication “pressure” over time?
@MDMarra Our core issue is that Log LUNs are filling up at an abnormally high rate, and so I guess I need to figure out which mailbox-specific metric relates to logs created.
Jul
7
comment What is the correct way to track and monitor Exchange DB replication “pressure” over time?
@MDMarra All disks are the same. The problem I'm seeing is that our bandwidth isn't capable of maintaining a realistic RPO due to many logs being created. This results in one particular database lag behind the others. I would rather spread out the load across all databases so that this one DB doesn't stick out during a failover event... and may need to be restored from tape because replication is.. well useless for this DB.