Give another employee access to OneDrive and Outlook data

You can also grant access to another user to access a former employee's OneDrive. Sign in to the admin center as a SharePoint admin. If you get a message that you don't have permission to access the admin center, then you don't have administrator permissions in your organization. In the left pane, select Admin centers > SharePoint. (You might need to select Show all to see the list of admin centers.) If the classic SharePoint admin center appears, select Open it now at the top of the page to open the SharePoint admin center. In the left pane, select More features. Under User profiles, select Open. Under People, select Manage User Profiles. Enter the former employee's name and select Find. Right-click the user, and then choose Manage site collection owners. Add the user to Site collection administrators and select OK. The user will now be able to access the former employee's OneDrive using the OneDrive URL. Revoke admin access to a user's OneDrive You can give yourself access to the content in a user's OneDrive, but you may want to remove your access when you no longer need it. Sign in to the admin center as a SharePoint admin. If you get a message that you don't have permission to access the admin center, then you don't have administrator permissions in your organization. In the left pane, select Admin centers > SharePoint. (You might need to select Show all to see the list of admin centers.) If the classic SharePoint admin center appears, select Open it now at the top of the page to open the SharePoint admin center. In the left pane, select More features. Under User profiles, select Open. Under People, select Manage User Profiles. Enter the user's name and select Find. Right-click the user, and then choose Manage site collection owners. Remove the person who no longer needs access to the user's data, and then select OK. https://learn.microsoft.com/en-us/microsoft-365/admin/add-users/remove-former-employee-step-5?view=o365-worldwide

Steps to setup IPSEC tunnel between Site 2 Azure Cloud

Steps needed to setup the VPN: 1.) Virtual Network Gateway 2.) Virtual Network 3.) Local Network Gateway 4.) Public IP address 5.) Connection Refereence: https://www.youtube.com/watch?v=hKgEjqTp8MI&list=WL&index=2&t=3s

Reset ESXi 6 Evaluation License

Reset ESXi 6 Evaluation License (cron script included) December 17th, 2015 / 2 min read / Edit Virtualisation #cron#esxi#evaluation#license#reset#script Commands Automatic Script For testing and educational purposes only. The ESXi 6 evaluation license is valid for 60 days and a free one can be obtained from VMware at anytime. Resetting the evaluation license provides continual access to all the features available, and most importantly for me, full compatibility with the ESXi Embedded Host Client. Commands Note: Running these commands will cause ESXi to appear offline/down. For example, my UPS virtual machine connected to my actual UPS began shutting down VMs because it believed ESXi ran into a problem. Shut down those VMs firstly before running this command then bring them back up later. Turn on SSH and log in to the host. Remove the current license rm -r /etc/vmware/license.cfg Copy over the new evaluation license, which is already on the host cp /etc/vmware/.#license.cfg /etc/vmware/license.cfg Restart ESXi services /etc/init.d/vpxa restart Confirm the new license Automatic Script The commands above can be run automatic to keep your ESXi license reset on a set schedule using cron. I have also created a script which powers off and on a VM of your choice (such as a UPS agent) in case it shuts down the host. First create the script (reset-eval.sh) somewhere accessible to ESXi. I chose to put in my ZFS0 datastore (/vmfs/volumes/ZFS0/reset.eval) #!/bin/sh ## remove license echo 'Removing License' rm -r /etc/vmware/license.cfg ## get a new trial license echo 'Copying new license' cp /etc/vmware/.#license.cfg /etc/vmware/license.cfg ## restart services echo 'Restarting VPXA' /etc/init.d/vpxa restart This alternative script shuts down any VM called 'ups-agent'. You may edit that line to your VM's name #!/bin/sh # This script shuts down the UPS-Agent and resets the license echo 'Getting VMID of UPS-Agent' vmid=$(vim-cmd vmsvc/getallvms | grep ups-agent | awk '{print $1}') echo 'VMID is' $vmid echo 'Getting UPS-Agent Power state' state=$(vim-cmd vmsvc/power.getstate $vmid | grep Powered) echo 'VM is currently' $state x=1 while [[ "$state" == "Powered on" && $x -lt 3 ]] do echo 'Powering off...' vim-cmd vmsvc/power.shutdown "$vmid" echo 'Waiting for VM to power off...' i=30;while [ $i -gt 0 ];do if [ $i -gt 9 ];then printf "bb$i";else printf "bb $i";fi;sleep 1;i=`expr $i - 1`;done state=$(vim-cmd vmsvc/power.getstate $vmid | grep Powered) x=`expr $x + 1` done if [ "$state" == "Powered off" ] then ## remove license echo 'Removing License' rm -r /etc/vmware/license.cfg ## get a new trial license echo 'Copying new license' cp /etc/vmware/.#license.cfg /etc/vmware/license.cfg ## restart services echo 'Restarting VPXA' /etc/init.d/vpxa restart #echo 'Restarting Services' #services.sh restart ## power on echo 'Powering on USP-Agent' vim-cmd vmsvc/power.on "$vmid" else echo 'Could not turn off UPS-Agent' fi echo 'Finished' Test the script and make sure it works (remember to chmod +x) $ chmod +x reset-eval.sh ./reset-eval.sh Add the script to the crontab to make it run on a set schedule (mine is set at 6:05am each day). For each 59 days do * * 59 * * /bin/echo "5 6 * * * /vmfs/volumes/ZFS0/reset-eval.sh" >> /var/spool/cron/crontabs/root kill $(cat /var/run/crond.pid) crond Finally add the following to the end of '/etc/rc.local.d/local.sh' to regenerate the job as ESXi clears the crontab on reboot /bin/kill $(cat /var/run/crond.pid) /bin/echo "5 6 * * * /vmfs/volumes/ZFS0/reset-eval.sh" >> /var/spool/cron/crontabs/root crond

Exporting mailbox PST off M365 / O365

 https://medium.com/@furkanakyol/microsoft-365-panel-%C3%BCzerinden-users-pst-export-nas%C4%B1l-yap%C4%B1l%C4%B1r-1318b43f5ecc

icrosoft 365 offers a range of services that make the daily work of businesses and individuals easier. These services include email, file storage, communication tools and many other applications. The user data of these services, especially email messages, can grow over time and this data may need to be backed up and archived. At this point, exporting users' PST files via the Microsoft 365 panel becomes a very important issue.

First, it’s important to understand what PST files are and why they need to be exported. PST files are Outlook data files that typically contain data such as email, calendar, contacts, and tasks. Exporting this data can be done for purposes such as backup, data migration, or archiving. Backing up and archiving data, especially related to user accounts, is essential to prevent data loss and to be able to access this data when needed.

It is very easy to export user PST files via Microsoft 365 panel. Here is a step by step guide on how to do this:

#Microsoft #Microsoft365

O365 deployment in RDS environment

 

Install Office 365 in a Remote Desktop Services Environment

 Microsoft, Microsoft 365, Office 365, Remote Desktop Services (RDS) Add comments

Mar302020

 

Once you deploy Remote Desktop Services (RDS) for employee remote access, your next step will be to install user applications as well as all your line of business applications.

One of the most widely used applications suite is Microsoft Office, particularly Microsoft Office 365.

In order to deploy Microsoft Office 365 in a Remote Desktop Services environment, a number of requirements must be met. There is also special instructions which must be followed to properly deploy it.

This information also applies when you want to install Office 365 / Microsoft 365 to a shared virtual machine or a golden image for VDI (for VDI you can read my full guide “Deploy, Install, and Configure Microsoft Office 365 in a VDI Environment“).

After reading and completing the steps in this blog post and deploying Office 365, you can head over to my guide on how to Configure Office 365 in a Remote Desktop Services Environment using GPOs to pre-configure Microsoft Office and it’s applications for when your users log in.

What’s required

To deploy Microsoft Office 365 on a Remote Desktop Services Server, you’ll need:

• A Remote Desktop Services Server (Configured and Running)
• Microsoft 365 Apps for Enterprise (formerly named as Office 365 ProPlus)

Licensing

Special attention must be paid to licensing. In order to properly license and activate Office 365, you’ll need one of the following products that supports Shared Computer Activation:

• Microsoft 365 Apps for Enterprise (formerly known as Office 365 ProPlus)
• Office 365 E3
• Office 365 E5
• Microsoft 365 Business Premium

All 4 of these products include and support “Shared Computer Activation“.

Microsoft 365 Standard, Office 365 Business, Office 365 Business Premium, and Office 365 Business Essentials cannot be used as they do not include or support Shared Computer Activation.

An exception is made for Microsoft 365 Business Premium which actually includes Microsoft 365 Apps for Business, but doesn’t support enabling “Shared Computer Activation” via Group Policy Objects and must be done using the XML configuration file method.

Installing Office 365

Once you have the proper licensing and you’re ready to proceed, you can start!

1. First you’ll need to download the Office Deployment Tool from this link: https://go.microsoft.com/fwlink/p/?LinkID=626065. You save this wherever.
2. Create a directory that you can work in and store the Office 365 installation files.
3. Open the file you downloaded from the Microsoft Download site, extract the files in to the working directory you created in step 2.
4. Open a Command Prompt, and change in to that working directory.
5. We’re now going to run the tool and download the x64 image using the xml that was extracted by running the following command:
   

   setup.exe /download configuration-Office365-x64.xml

   To download the 32-bit version or enterprise version, use one of the other xml files that are in the directory.
6. There will be no output and it will take a while so be patient.
7. Now we want to open the xml file we previously used (in our case “configuration-Office365-x64.xml”) and add the following lines to the file right above the final line (right above </Configuration>):
   

   <Display Level="None" AcceptEULA="True" />
   <Property Name="SharedComputerLicensing" Value="1" />

   These variables enable Shared Computer Activation and disable automatic activation. Save the file.
8. We can now install Office 365 by running the following command:
   

   setup.exe /configure configuration-Office365-x64.xml

Office 365 should now install silently, and then afterwards you should be good to go!

When a user logs in for the first time it will ask them to activate on their account. The user must have a license attached to their Office 365 account.

For more information and advanced settings, you can see the Microsoft guide here: https://docs.microsoft.com/en-us/deployoffice/deploy-office-365-proplus-by-using-remote-desktop-services.

You are now ready to proceed to Configure Office 365 in a Remote Desktop Services environment, so that everything is configured and ready to use when your users log in.