Add new domain to office 365 portal(2)

Today, I’ll show how to confirm domain which I want to add office 365 portal using powershell.

It is so easy to confirm domain which I want to, because I’ve already added txt record to dns management site, so if I use Confirm-MsolDomain cmdlet, it shows successfully verified.

confirmdomainif you excute that powershell, you can get values, Availability, AvailabilityDetails, it shows “The domain has been successfully verified for your account.”

showmessages, If I go to see dns status, it shows the status is “setup in progress”, so it looks theare are more jobs to proceed such as “Set up as Default”, so as to set domain as default, I use Set-MsolDomain cmdlet with IsDefault option like below image.

setdomaincmdlet.pngthen if you go to admin page about dns, you can show my new domain have set “Default”

setasdefaultdomainIf I see new domain status on admin page, it shows “Setup in progess”, what should I do next? In my case I did add wrong values to dns , so as to work well, it needs to clean up

Add new domain to office 365 portal(1)

Today I’m explaining how to add new domain which I have owned to office 365 using powershell.

newDomain.png, if you execute those powershell, I can get Text record value like this.

txtRecord1.png

In this post describes using New-MsolDomain cmdlet, to get txt record value, I am using Get-MsolDomainVerificationDns cmdlet.If you use Get-MsolDomainVerificationDns cmdlet, you can get DNS record that needs to be set to verify a domain.

Then I go to godaddy site to add txt values which I get from using that powershell, I added it.

Even if I go to my office 365 admin center, it added ysahpro.com as status of “Setup in progress”

admin_domainpage

Next post I’ll confirm my domain using powershell, it may use “Confirm-MsolDomain”cmdlet, it looks like awesome using powershell

 

 

How to check your tenant name in office 365

Yesterday I bought one domain to use my office 365 temp tenant from godaddy, before buying domain from godaddy, I think it was expensive but that site have more cheaper domain to use on my own.

Normally if I add domain to office 365, I usually use office 365 admin page, but today I’ll go proceed using only powershell.

Before adding domain, it needs to check it first, what is my tenant name? You can check it if you go to sharepoint on admin center as manually.

tenantname1  Then if the sharepoitn admin center open, you can now what is your tenant name, my tenant name is “cloudwide1610”

tenantname2

or based on our original plan, if you use get-msolaccoutsku cmdlet, you can see easily check what is your tenant name.if you see yellow circle, you can know it.

gettenantnameps

I’ll make posts to add domain using powershell.on office 365 environment. Thank you for reading my posts.

 

 

Managing Active Directory ProxyAddresses in PowerShell

Today, I introuduce how to set or manage ActiveDirectory ProxyAddresses using PowerShell not ADSI Edit tool. Before this job, I am ususally using ADSI Edit tool, if I just set that value some users, it is ok, but sometimes if we create bulk users more than 10 people, it’s burden to using ADSI Edit tool, also if you have any experience to using that tool, it’s hard to use it to find members which I set values.

So as to set that values using powershell, I have studied and searched from internet a lot.Strangely it takes time a lot to find that solution

Import-Module ActiveDirectory #importing active directory powershell module

$csvFilePath = “C:\NewUsers.csv”

Import-Csv -path $csvFilePath | ForEach {    #get values from csv using ForEach ,

        $SAM = $_.SamAccountName   #SamAccountName as field name of csv file   
        $UPN = $_.UserPrincipalName  #UserPrincipalName as field name of csv file
        $proc = “SMTP:”+ $UPN                  
#Adding proxyAddress to user , if you remove that value you use remove instead of Add properties
        Set-ADUser -Identity $SAM  -Add @{ProxyAddresses =  $proc }
        Get-ADUser -Identity $SAM -Properties ProxyAddresses | Select-Object Name,ProxyAddresses
}

Have a great day and thank you for reading my blog post.

Using Invoke-Command for Remoting

When I execute using Invoke-Command cmdlet to get value from remote machine eventlog for parallel result , I got error, “Connecting to remote server “” failed with the following error message : The client cannot connect to the desitnation specified in the request. Verify that the server on destination is running and is acceptinig requests. Consult the logs and documentation for the WS-Management service running on the destination , most commonly IIS or WinRM. If the destination is the WinRM service, run the following comand on the destination to analyze and configure the WinRM service; “winrm quickconfig”~
pswinrmerror So as to communicate it , I run “Enable-PSRemoting -Force” on destination server’s powershell, then when I execute again to get value more fast against using get-eventlog cmdlet, it executes well and get values.psremotingforce

Windows Remote Management (WinRM) is implemented by Microsoft, it use WS-Management protocol, we can connect local computer and remote computer using web service as securely.

Invoke-Command : Runs commands on local and remote computers and returns all output from the commands, including erros. By using a single Invoke-Command command, you can run commands on multiple computers.

 

Check Office 365 services provisioning status

Hi, Today I’ll introduce how to check office 365 services are provisoned or provisioing. When we assign new licenses to office 365, services related to license are provisioned, sometimes it takes time half an hour or 1 day, so if you can see status of provision of services related to office 365 licenses, it may help to check the current status and what services you can use or you can’t use.

If  you use Get-MsolUser cmdlet, you can use then check services status.

Example)

PS C:\> (Get-MsolUser -UserPrincipalName test@ysah.org).Licenses[0].ServicesStatus

pending3.png Above this Service status  said , Exchange_S_STANDARD is PendingInput , it means if you start outlook under OWA, you can see below message “Error: You cannot open mailbox, it may the mailbox license was expired, so if you check how to get access authority of this mailbox, you ask your mail administrator” exchangeError.png If it takes time , when you check service status, you can see most of services are success to open it.provision2.png

I hope you can reference this link to check services status which you recently assigned. https://blogs.technet.microsoft.com/cloudpfe/2013/12/27/how-to-tell-which-office-365-services-have-been-provisioned/

I

Office 365 Deployment for office 2016 Creation

Hi, Today I’ll introduce how to make office 2016 fille for office 365 deployment to share users as network drive. Recenltly as you know Microsoft introduced and changed to streaming install using click to run, but in this case it is beneficial to have enough bandwith I think, but on the network bandwith as company , it is not good solution. So as to distribute this tools for users, you have to make office 365 ProPlus , if you see documents, plesae move to here. https://technet.microsoft.com/en-us/library/jj839718.aspx

Procedures

  1. You can download Office 2016 Deployment tool , if you execute it then it needs to select folder to extract setup.exe and configuration.xml
  2. You can make configuration configuration.xml referenced by configuration options for the office Deployment tool (Link), in my case updated below  , I just want to make  32bit office 365 proplus for office 2016 with as language of Korea to see the status of installing with progress bar, completion screens, error messages, or other user interface are disabled. And the user does not see a Microsoft Software License Terms dialog box anymore , to define how office is updated after it’s installed.        <Configuration>
    <Add SourcePath=”s:\O365_2016\setup\” OfficeClientEdition=”32” >
    <Product ID=”O365ProPlusRetail“>
    <Language ID=”ko-kr” />
    </Product>
    </Add>
    <Updates Enabled=”TRUE” UpdatePath=”s:\O365_2016\setup\” />
    <Display Level=”Full” AcceptEULA=”TRUE” />
    </Configuration>
  3. Open Command Prompt as administrator mode, then move to that folder to download installer file using setup.exe /download configuration.xml , if you execute it, it download full installation file to that folder.
  4. When completes to download full package to install, you make batach file to execute with /configure option, it describes setup.exe mode on the inline imagemode-for-odt, I made batch file using setup.exe /configure configuration.xml , then I distributed to our network folder to users.

If you do go on Office 2016 Deployment Guides for Admins (Link), then read full of it, and you can make your own office 365 proplus