Are there published standards for who appears in the Outlook global address book in a hybrid Office 365/Exchange environment? Like disabled users, users with only a phone number, contacts in a non-synced OU, etc.
Note that we can manually change the settings in a mailbox to hide the user from address lists but a better solution would be to understand who appears and manage them holistically.
In a hybrid Exchange environment, if you migrate a user mailbox and then they attempt to access the mailbox using the on-prem OWA (Outlook Web App) link, they will be presented with a page that instructs them to click another link to reach their mailbox and offers a button to create a favorite to the new OWA on O365. Can this redirection page be modified to change the wording, add branding or remove the button to add a favorite?
What's the best way to confirm to an auditor that a change made to any permission in Exchange was actually made by a legitimate admin with an approved change ticket?
We were recently asked to implement Manage Engine's "Exchange Reporter Plus" and to set it up so that it notifies the whole team of any change to permissions on any account. The person responsible for making that change is then supposed to respond to the email to say why the change was made and what the ticket number was. That will satisfy the auditors, they say.
But that is a REALLY laborious process to dig up a ticket number and email it out to the team for every single change. Surely other companies have this requirement and have come up with better solutions, right?
I'm using PowerShell to create mail contacts (external users, not employees) in Exchange 2013 but they are automatically being assigned internal addresses according to the mailbox policies.
For example, I create a contact called "Test User" with an email address "[email protected]". The contact is created and the primary address is the google address as expected. In addition, the default policy is applied and adds an address like "[email protected]" to the contact's alternate addresses. If I delete it, it's reassigned immediately.
The problem is that 6 months later when I hire an employee who should receive the valid address "[email protected]", it's unavailable and he gets "[email protected]". If I re-apply rules strategically, I can give him the address I want and give the contact an invalid address instead but that's a lot of work and it all gets peeled back if another admin re-applies in the wrong order afterward.
So - why are email policies applied to contact objects in the first place? And can you stop that from happening?
I have a number of mail users (valid AD accounts with outside email addresses) and am in a hybrid Exchange environment with Office 365 and our on-prem server. The email addresses showing up in our on-prem system are just the external addresses we've assigned ([email protected]), as expected. But once the mail user gets synced to Office 365, it adds an internal address ([email protected]). Then later, when we have new users with similar names, that address has already been taken in O365 and we can't sync them. I also can't remove the extra addresses since the object is synched from on-prem, yet the additional addresses aren't assigned on-prem...
How do I stop O365 from creating internal email addresses for the mail users?
Thanks,
I'm trying to use the following command (without the line break) to relay email through an Exchange 2013 server from another server. The sending server is listed with explicit permission to relay anonymous email and the same command used to work a few months ago.
Send-MailMessage -To [valid email group] -From [throwaway address]
-Subject "Test Only" -SmtpServer [valid URI to server] -body "Testing"
The result of the command is that nothing happens. No error, no email, nothing. I'm not the Exchange admin and he says we've installed updates and such but we can't correlate one update or session to this failure. Any troubleshooting tips? Thanks.
I can use Powershell and the Get-VBRBackup and Get-VBRJob commandlets to get the status of a back up job. But i want to verify an individual server has been backed up in the last 7 days. Is that possible with Powershell?
How can I package office 2010 applications individually for distribution via SCCM 2012?
I can package the office suite with no problem using an MSP file to customize it, but if I install only Excel for example using setup.exe /adminfile excelonly.msp, I can not later run the install again with a different MSP file to add Word to the existing installation.
Error I get is:
The /adminfile command-line option can be used only during initial installation of the product.
I want to install Forefront Endpoint Protection on my SCCM server using a new service account that I just created specifically for this purpose. I'll be using a separate reporting database so I'll need to grant the account rights there too I assume but I can handle the SQl end of it.
I've created the AD account and copied my existing admin permissions in the SCCM console. I also added the account to the local "SMS Admins" group. But I can access "Site Management" with my admin ID. The new service account can not. So I assume there's other differences that may impact my FEP install.
So how do you grant full admin rights in SCCM?
I'm using the Quest commandlets for a very simple and straightforward update but it's not working. No errors, it just fails to change the value:
Set-QADUser ttest -ObjectAttributes @{office="ABQ"}
Can't get much simpler - what am I doing wrong? both of these work fine:
Set-QADUser ttest -objectAttributes @{otherTelephone=@('555-34-67','555-34-68')}
Set-QADUser ttest -objectAttributes @{otherTelephone=''}
but this does not:
Set-QADUser ttest -objectAttributes @{extensionattribute2="test"}
When a meeting is created that conflicts with another meeting on the Room calendar, is it possible to have the conflicting meeting forwarded to a delegate for a manual resolution?
I'm working on a dynamic page that does data lookups based on metadata in the term store. So I have a Managed Metadata column set up and I can use it to query lists and such with no problem. I also have an image library with a managed metadata column that I use to return relevant images.
The problem is that I, as a farm admin, can see and edit all the metadata in my image library. Normal users with read rights see a blank field. They get no results from the lookups, as if the metadata was blank. I even made a user a site collection admin and he can add metadata, but not see it in any view or the object property page. He only sees it on the edit page.
My metadata service is set up normally, the content hub is running without issue, no errors on the page. Publishing is disabled so it's not approval thing. Anyone seen anything like this before?