Copilot for PowerBI

Copilot for PowerBI is now coming out in preview, and the feature will be enabled for all tenants. The feature can enhance data interaction and report creation using generative AI. If the organization is not ready for this roll-out, there are ways to restrict this feature based on security groups. There are controls to include or exclude groups.  One concern organizations have is the possibility of data being processed in a datacenter in a different region than their tenant. This can also be controlled by not allowing the usage of datacenters outside your region. Sign into the admin portal for PowerBI and check the settings associated with Copilot

Installing OCS 2007 R2 on Windows 2008 R2

#OCS #WindowsServer #Powershell

Here is a tip for if you want to speed up the process of installing OCS on a Windows 2008 R2 server.

The installation wizard and guide is made for previous OS's, and is not capable of detecting or installing all of the features you need (.net framework beeing one of them). Also, I realized all the tech blogs I came across on google suggested to use the servermanagercmd.exe to add some of the prerequisites. servermanagercmd is depreciated, and I suggest you use Powershell in Windows 2008 R2.

So, before even thinking of starting the OCS setup, you should concider running the following commands in powershell (as administrator):

import-module servermanager
web-windows-auth,web-mgmt-compat,web-mgmt-console,web-http-logging,msmq-server,msmq-directory,rsat-addc,was-process-model,was-config-apis,NET-Framework-Core,Desktop-Experience -restart

So far, so good, but now I,m stuck with a new error: 0x80070534 "No mapping betweein account names and security IDs was done. This error is registered on the "setting NTFS rights" section in the error report. Anyone got an Idea?


PS: I know OCS 2007 R" isn't yet supported on Win 2008 R2 server, but I'v heard of other sucessful installations and wanted to test it myself
Anonymous said…
I was getting the same error. I was using a virtual (vmware) environment for my lab setup, and was cloning a snapshot of base installation of Windows Server 2008 R2 and then trying to install OCS 2007 R2 on it. The problem was that when you clone from a snapshot in vmware the clone receives the same SID as the original. I had unjoin the clone from AD domain, run sysprep and join the my virtual lab AD domain again. Only after this did this error go away and OCS 2007 R2 was successfuly deployed on Windows Server 2008 R2. Hope this helps.
Here's an update: