User Profile
DeepakRandhawa
Iron Contributor
Joined May 03, 2019
User Widgets
Recent Discussions
Re: Authentication-Results-Original email header
Authentication-Results-Original are from previous mail server. Authentication-Results are results of last receiving servers' email auth checks. You can paste email header into dmarctester.com and find the status of SPF,DKIM and DMARC. MXToolBox Message Analyzer has a known issue where it usually fails DKIM.Re: Difference between Usermailbox vs Office365 mailbox - Exchange Hybrid
You need to create user in local AD, there is no way of syncing a user from O365 to on-premises, it only supports syncing of very few user attributes. Once you have created user in local AD, run Enable-RemoteMailbox SamAccountName -RemoteRoutingAddress User@domain.com This creates a remote mailbox, now after one sync cycle of AAD Connect, assign the license to user in O365. Now you have both, a user mailbox in O365 and a remote mailbox in you local exchange.Re: AADconnect with Exchange server but without Hybrid Config - Managing users
Hey LIT-RS Yes, this need to be run for each mailbox. Yes, this is to see existing O365 mailboxes in on-premises ECP. Not sure what you read about Set-MailUser, I think it is irrelevant in this context. You can follow the same process that you have been following till now to create new mailboxes and then run this command for each new mailbox that you create. DeepakRe: AADconnect with Exchange server but without Hybrid Config - Managing users
Hey LIT-RS, You should be able to use below cmdlet :- Enable-RemoteMailbox samaccountname -Remoteroutingaddress mailto:alias@domain.com This should allow you to see the mailbox in on-prem console as a Remote Mailbox. Hybrid is not required to run this cmdlet. I'd recommend to test this with a test user first. DeepakRe: Help....TAsk scheduler asking for credentials
Hello vaibhavkaulkar, Here's a step by step process:- - First Open Powershell and use below cmdlet to generate an XML file with credentials:- Get-Credential | Export-Clixml -Path "C:\Users\UserName\Desktop\Data\Cred.xml When you will use this you will be prompted to enter your credentials, just enter your credentials in the pop up box that appears, once you do you will be able to see an XML file at the location provided in the above cmdlet in the -path parameter. If you open the XML you will see that it contains your username in plain text and your password in encrypted text. Please remember to generate the XML file with same User profile on the same Computer where you will be using them as credentials are encrypted using the Windows Data Protection API and can only be used by user who generated them and on the computer on which they were generated. - Second step is to start you SP script with below cmdlets :- Start-Transcript Import-Module Microsoft.Online.SharePoint.Powershell -DisableNameChecking Import-Module ExchangeOnlineManagement $Cred = (Import-Clixml "C:\Users\UserName\Desktop\Data\Cred.xml") $AdminCenterURL = "https://xyz-admin.sharepoint.com/" Connect-SPOService -Url $AdminURL -Credential $Cred Connect-IPPSSession -Credential $Cred #create temp folder if it does not exist $ReportOutput="C:\Temp\pvtSiteColl.csv" #Get All site collections ........ ThanksRe: Help....TAsk scheduler asking for credentials
Hello vaibhavkaulkar Have you tried storing creds in an xml first, it is generally not a good idea to expose creds in the script. If you want to try this, you can do below:- -First store creds in an xml file Get-Credential | Export-Clixml -Path "C:\Users\UserName\Desktop\Data\Cred.xml" -Then Call them to connect your SP session $Cred = (Import-Clixml "C:\Users\UserName\Desktop\Data\Cred.xml") Connect-SPOService -Url $AdminURL -Credential $Cred Hope this helps !!!Re: Microsoft 365 ohne Exchange
FlorianKurrle Yes you can do that too, however letting AAD Connect sync your users to O365 is the best option. To not assign a mailbox to a user ,when assigning license to them, remember to uncheck the Exchange Online ( Plan 1 or Plan 2 depending upon your license ) under Apps.Re: Office365 subdomains
Once you add and verify test.dom.com, you can add sub.test.dom.com. During the domain add process you will be provided with DNS records that you need for mailflow, you just need to add those to your public DNS. Azure AD can manage your domains correctly as long as you set them up correctly and add the required DNS records correctly.Re: Office365 subdomains
You just need to verify domain test.dom.com in O365, once you do you can add multiple subdomains. So if you have already verified test.dom.com in O365 you can add sub.test.dom.com from 'Domains' option under 'Settings' in Admin Portal and no additional verification or TXT record is required to prove ownership of this subdomain. However you still need to add MX and other records for mailflow and autodiscover to work correctly for this subdomain.
