HackSlash's questions

There are many old questions related to this targeting Exchange 2010 on premises. If you're using Exchange Online in Azure, things have changed. Now you will need the new REST API remote PowerShell commands to manage Exchange. Accessing the properties on these objects is very different.

I can't find the account enabled property anymore and while there are Get-EXO* methods I don't see the corresponding Set-EXO* commands. The documentation doesn't talk about how to set properties on mailboxes, only to look at them. That can't be right.

I do see the HiddenFromAddressListsEnabled property but I can't change it.

BACKGROUND:

We generally disable accounts when people leave but we want to keep their mailbox. At the same time, we don't want that mailbox to be visible in the GAL. This will lower the chance of someone sending email to a person that doesn't exist.

QUESTION:

1. How do I remove all currently disabled users from the GAL?
2. How do I automatically remove users from the GAL in the future, as part of the account turn down process?

Can both be accomplished by a single method?

We need to block Logitech Unifying dongles now that it's public knowledge you can both sniff\decrypt keystrokes, and also inject keystrokes.

Is there an easy way to block these common dongles with GPO or InTune?

All I have so far is a PowerShell script to disable devices but this would have to be run after the device is plugged in, which is reactive and not preventative.

# Disable Unifying receivers
Get-PnpDevice -FriendlyName "Logitech*" -Class 'Mouse' | Disable-PnpDevice -confirm:$false

If you use FMAudit to collect printer usage data it will accumulate junk devices over time. Not just old printers but it picks up many things that respond to SNMP query.

As of version 4.1.3 the GUI still doesn't offer an option to remove old devices! The only forum post I can find talking about this issue says the solution is to reinstall. That doesn't sound ideal.

How do I remove old devices?

We needed to add a warning to all emails sent outside the organization. I went in to the M365 Exchange Admin center, under mail flow > rules, adding a rule that appends a disclaimer to every message sent outside the organization. Great, check that box for a job well done.

In practice, if you have a long email chain with an external contact you will find these disclaimers piling up at the end. The duplicate disclaimers can be quite overwhelming and much larger than the actual content of the messages themselves. Seems wasteful.

I need some way of avoiding duplicate disclaimers on a message that already has a disclaimer.

FROM THE LINK IN THE COMMENTS:

For example, to add the exception that prevents multiple disclaimers being added in an email conversation, select Add exception and then select The subject or body > Subject or body matches these text patterns, and then specify the words or phrases in your disclaimer.

I guess I am looking for a better description of how that is done. The exception language says "matches these text patterns" and the documentation says that this "pattern" is a Regular Expression. So I need a RegEx that matches my disclaimer without accidentally matching other strings of words.

QUESTION:

How can I troubleshoot and fix Outlook 2013 Clients so that they can pull MailTips, set Out of Office notifications (Automatic Replies), and see Free/Busy availability?

DETAILS:

The server is Exchange 2010 build 14.03.0361.001 running on Server 2008R2. Outlook 2016 works 100%, with no problems. All features work from OWA. This would suggest that the server is capable of serving Exchange Web Services (EWS). Users who are on Outlook 2013 or below cannot see MailTips, OOF, Free/Busy Availability. I've found that there are a large number of causes for these errors. I'm interested in the behavior difference in Outlook 2016 that would allow it to pull from the server when 2013 clients cannot.

RELATED ERRORS:

When attempting to set Automatic Replies (Out of Office)

"Your automatic reply settings cannot be displayed because the server is currently unavailable"

When writing a new message

"We can't show MailTips right now"

When attempting to schedule a meeting

"Suggestions cannot be provided because free/busy data could not be retrieved."

Scheduling Assistant shows "No Information" for all invited attendees.

WHAT I HAVE TRIED:

• I have gone through all the AutoDiscover\AutoConfiguration troubleshooting and I have found that all of my URLs are correct and AutoDiscover works fine.
• I have ensured that DNS is set up correctly with SRV records for AutoDiscover.
• I have tested the URLs in AutoDiscover from affected clients and they can pull the XML files with no problem.
• I have tried creating new Outlook profiles on affected systems.
• Rebuild the EWS Virtual Directory on the Exchange server
• I have read through countless articles and searched all the forums, both official and rando.

On step #8 of the GUI installer there was no Network in the top drop down at all. Because of this when I attempted to proceed past this point I was met with:

No networks on the host. Cannot proceed with the installation.

The page looks like this:

What did I do wrong? How is it that I can query the datastore but no networks are available?

NOTE: I have searched for an answer to this already and the only thread that mentions this problem is from the VMWare forums and the answer was "You need to use standard switch to complete the upgrade process." This answer doesn't make sense as all of my switches are standard. None are distributed.

PROBLEM:

Access to the shares work when the network is "Public Network" or "Private Network" but not when it is "Domain Network".

QUESTION:

What different things change with the Network Location type, aside from firewall settings?

BACKGROUND:

I have some strange proprietary machines that connect using SMBv1 using very old protocols. I have shares set up for them in a Windows 2008 R2 and it was working just fine. I had to change some security options to allow LM & NTLM authentication. When I first got it working the network was erroneously identified as "Public Network". At some point, a Windows update fixed this and now it is correctly identified as "Domain Network". The machines can no longer connect. I got it to work again by changing the Network Location to "Public" but it breaks on each reboot. I really need to know why the shares change with the network location but I can't seem to find any information about that.

NOTE:

I have tried turning the firewall off. All of the "Advanced Sharing Settings" are identical for all 3 network profiles. What else changes?