This is a simple powershell to get data from the DirectAccess database. It reguired some serious Bing’ing (and google) to get the time field. You will have to configure reporting database in DirectAccess config. I used windows internal database.
#$query="Select * from $table" #$query="Select * from $database.INFORMATION_SCHEMA.TABLES" $query="declare @start bigint=131277336299720000;select dateadd(mi,datediff(mi,getutcdate(),getdate()),([sessionstarttime]/864000000000.0-109207)) AS DATO,* from sessiontable join connectiontable on sessiontable.connectionid=connectiontable.connectionid where sessionstarttime &gt;=@start"
Would it be nice to list all leakedcredentials using powershell?(or riskysignins or identiyriskevents). All of this could be achieved using powershell and REST api at Microsoft Graph. I have a scheduled task running to get this reports. Using a appilcation in Azure. All credentials are stored in SecretServer. First we need an Application Registration in Azure.
After we have created the AppReg. Add a password, app key. Combined with the application id this is our username and password.
Now it is time to give this app the required permissions from microsoft we can identify witch permissions are needed to run this query. https://developer.microsoft.com/en-us/graph/docs/api-reference/beta/api/leakedcredentialsriskevent_get
Next would be to set the enterprise application to “user assignment required” and “Enabled for users to sign-in.” also “Hide it from users.
Now we are ready to start with our powershell script.
Ran into a issue where Skype for Business frontend service refused to start. It remained in starting for ages before giving up. In the event viewer the statement was : Server startup is being delayed because fabric pool manager is initializing. This event seemed to have something to do regarding pool, but this was a standardedition Skype for Business setup containing one frontend and one edge server.
Many articles on Bing and Google explained how this could be a issue with the certificates on the server, but in our case the frontend server and edge server was happily replicating the topology. We started by trying to do as the event told us:
But this also failed. For me it looked like there was something wrong with WindowsFabric. Compared with another SfB server and in taskmanager I could see fabric.exe running, but not on on the server with the issue. Looking in eventviewer Microsoft/WindowsFabric Admin:
At first I tried to install Windows Fabric from SfB install media. But same error. Then we tried to uninstall and reinstall. This resulted in a more serious error. Now the server has lost its connections to the Fabric. So how do we fix this. My solution was to uninstall SfB frontend server module and then run the Deployment wizard to reinstall it with config from the management store. This worked perfect. The front end service started immediately.
After we installed office 365 on our pc’s we discovered high disk IO, especially on our terminal servers. Running tools from sysinternals this turned out to be something in Office installation called Telemetry, When we started office apps some file, in the profile folder structure, called OTELE was constantly updated. Not one file, but several.
After som time of investigation we found one registry key that seem interesting “DisableTelemetry”. The obvious thing to do was to set this value to 1 (binary enabled). But that did not help at all. When we started Oulook the value was set to “0”. Searching the internet gave us the answer from Microsoft (second hand 🙂 ) That this could not be disabled. But after a support case : It would have taken us forever to find the value. The answer is 170000 ,
Set the value to 170000 and all disk IO to OTelemetry stopped. Now our servers are back to normal, only a subset of files are created.Thanks to Jan Ove Aarnes for his findings.
When viewing large log files notepad (pre windows 10) is useless. Usually it is only the last lines of a log file that is interesting or to continuously trace the file. The answer is as always PowerShell.
If you are running Windows 2012R2 and install Lync server 2013 you might have problems starting Lync Management Shell. The Powershell Windows pops-up but no content appears. To get pass this I try to run PowerShell as Administrator and then run “import-module Lync”
After I install i new Lync 2013 solution I’m always so keen to start testing. One of the first things I do is to start Lync 2013 on my Windows Phone. As soon as I see the error Message “Please install Lync 2010 …” I know that I have forgotten to install the Lync Server 2013 CU…
We have tried several products, but for the time being PEXiP Infinity is our preferred choice. It is easy to deploy and the price seems right. Deployment of a new solution can be done in minutes. Upload the Pexip management node to your VMware host and use Pexip to deploy the number of conferencing nodes your solution would require – usually 1 or 2. As we all know Lync servers are rather strict when it come to certificates, so you will have to buy one sertificate for the main conference node. Also publish the normal Lync federation DNS records (srv record _sipfederationtls._tcp.your.domain 0 5061) for the Pexip system as it will pretend to be a Lync edge server. Now it is possible to call a pexip video conference room from Lync. In version 4, coming in April 2014,desktop sharing will be possible. Now that we have this pexip Virtual Meeting room – Cisco ,Polycom and Lync can Connect and share content.The only thing missing at the moment is a good solution to manager your Meeting, at the moment you will need a iphone or Ipad but this will change and become a web Interface.