These instructions assume you have access to a Kaseya VSA server (with the AuthAnvil module installed) and licensed for Enterprise Applications in Azure AD.

We will not be covering the details of the Enterprise App configuration outside of the SAML based setup.

Configuration – Azure AD

1. To begin log into your Azure AD tenant and open the Enterprise Applications settings.
2. Choose New Application at the top.
3. Then select “Non-Gallery Application” and give this a name.
4. In the left menu choose Single sign-on
5. Choose SAML as the option
6. Enter the Basic SAML Configuration section
   1. Identifier (Entity ID) for this we want to use the URL of your VSA server as a base and the rest of <vsaserver>/vsapres/web20/core/ssologin.aspx
      e.g:
      https://vsa.arweth.com/vsapres/web20/core/ssologin.aspx
   2. Repeat this for the Reply URL (Assertion Consumer Service URL)
   3. Leave the remainder empty (Sign on URL, Relay State, Logout URL)
7. Enter the User Attributes & Claims
   1. Name identifier value: This is what we use for the Kaseya user name.
   2. You want to delete all other entries from this section other than the one we use to sign into Kaseya with.
8. SAML Signing Certificate
   1. Enter the configuration for the certificate. You can use the default Azure generated one or upload a new one if you use your own certificate on different platforms.
   2. Set the signing option to Sign SAML response
   3. Signing Algorithm to SHA-1
   4. Set a notification email address to be notified when this certificate is due to expire.
   5. Download the certificate (Base 64) as we need this later.

Configuration – Kaseya VSA

1. From here we configure the AuthAnvil module in the VSA server.
   1. Go to AuthAnvil -> Two Factor Auth -> Configured Kaseya Logon
   2. Enter an AuthAnvil SAS URL just so this setting saves – we use a non-existing AuthAnvil on demand tenant as this still verifies the URL exists.
      https://nonexistant-disable.my.authanvil.com/SAS.asmx
   3. Tick the option “Enable Single Sign On to Kaseya”
   4. Set the reply to URL to the same as used in step 5.1 above
   5. Click “Select Certificate”
   6. Followed by “Choose File” and choose the certificate we downloaded in step 7.5 above
   7. Click “Import Selected Certificate” and confirm the certificate information supplied is for the correct certificate – if you used an Azure generated one this will have Azure details on it.
   8. Save the settings

Once you assign the application to users in AzureAD you should be able to log into the VSA with the enterprise application portal.

Troubleshooting

When this fails to work the sign in process will take you to the server login screen.

There are very few logs that assist with troubleshooting this.

One of the tools used when troubleshooting our configuration was the SAML-tracer plugin for Firefox: https://addons.mozilla.org/en-US/firefox/addon/saml-tracer/

This plugin when shows the SAML traffic and the data being passed to the Kaseya VSA server.
One of the main issues we encountered was getting the correct user claim passed in the SAML response.
This is because the user must match the internal Kaseya directory exactly.

The other main issue is to ensure your signing settings are correct as the VSA will not process these when set incorrectly.

Please comment here or reach out to me if I’ve missed something or a step is not clear.

The post Implementing AzureAD SSO for the Kaseya VSA appeared first on Arweth.

This appears to be occurring on files with more than one audio stream. Commonly found with NVIDIA ShadowPlay recordings.

A workaround to allow Vegas to process the file is to disable “Audio  Event Waveforms” from the view menu or pressing Ctrl + Shit + W.
This would need to be done from an empty project before trying to import the files causing the crash or before opening the project file.

This has been tested on Vegas pro 14.0 build 270.

The post Vegas Pro – Stuck Building Peaks Fix appeared first on Arweth.

Most places and sites list how to add and remove permissions but few mention how to edit / modify existing permissions on the calendars.

In the below example we will grant Bob, Author rights on Arweth’s calendar.

Add-MailboxFolderPermission arweth@arweth.com:\Calendar -User bob@arweth.com -AccessRights Author

This is straight forward however if you want to edit the above permission or change the level of access you need to use the following command:

Set-MailboxFolderPermission arweth@arweth.com:\Calendar -User bob@arweth.com -AccessRights Editor

If you attempted to use the add-mailboxfolderpermission command again Office365 would have returned an error similar to:
An existing permission entry was found for user bob@arweth.com

As a note to remove a permission you use the command:

Remove-MailboxFolderPermission -Identity arweth@arweth.com:\calendar -user bob@arweth.com

You can also check existing permissions with the following command:

Get-MailboxFolderPermission -Identity arweth@arweth.com:\Calendar

You can also add the -user to the get command to return the permission for one user.

Hopefully this helps with the permission management of calendars – these commands will also work for other folders and in some versions of Exchange on Premise.

The post Office365 Calendar Permissions through PowerShell appeared first on Arweth.

Update as of 11:50a.m 24th Aug GMT

Blizzard have advise this DDoS attack has subsided and is no longer impacting services.

The earlier issue affecting connections to our games/Bnet should now be resolved. Thanks for your patience.

— Blizzard CS – The Americas (@BlizzardCS) August 24, 2016

Update as of 10:38a.m 24th Aug GMT

Blizzard have advised of another DDoS attack against their services which have taken the systems offline again.

We are currently investigating a new series of DDOS attacks against network providers, affecting latency/connections to our games/Bnet

— Blizzard CS – The Americas (@BlizzardCS) August 24, 2016

Update as of 10:30a.m 24th Aug GMT

Blizzard have posted that the DDoS has subsided and services are running again.

The technical issues we were experiencing earlier have been resolved. Apologies for the inconvenience!

— Blizzard CS – The Americas (@BlizzardCS) August 24, 2016

Update as of 8:20a.m 24th Aug GMT
Battle Net is again under a DDoS attack which has taken the services offline. Battle Net appears to have been able to push notification through the Battle Net client and have provided updates on their Twitter feed which you can follow @BlizzardCS

We are currently monitoring a DDOS attack against network providers which is affecting latency/connections to our games.

— Blizzard CS – The Americas (@BlizzardCS) August 24, 2016

The latest update provided by one of the regional twitter handles for Blizzard states they are monitoring the situation.

We continue to actively monitor an ongoing DDOS attack against network providers, affecting latency/connections to our games. #BlizzCS

— Blizzard CS EU (@BlizzardCSEU_EN) August 24, 2016

When trying to reach the Battle Net webpage many of the attempts time out however some requests return a maintenance page which can been seen below.

Original Post:

Correction: The DDoS attack is against the upstream network providers that supply Battle Net and not Battle Net itself.

Frustrated users are unable to log into Battle net and are unable to get the Blizzard websites. The issues starting being reported by users around 11:20 a.m GMT.

A tweet by @BlizzardCSEU_EN confirms the Battle Net systems are under a DDoS and they are currently investigating.

We are currently experiencing issues with our community sites and forums. We will have them working again as soon as possible! #BlizzCS

— Blizzard CS EU (@BlizzardCSEU_EN) August 23, 2016

We continue to actively monitor an ongoing DDOS attack against network providers, affecting latency/connections to our games. #BlizzCS

— Blizzard CS EU (@BlizzardCSEU_EN) August 23, 2016

The Battle Net app is currently advising users they have been placed in a log in queue and provides an estimated wait time for the login to progress.
However many users are reporting on social media that the client is never logging in or reaching the end of the wait time.

At this stage no claim of responsibility has been made.

Further updates to follow as more information emerges.

Update: 2:40p.m 23rd Aug GMT Blizzard have advised the DDoS has subsided and services should now be operating normally.

The technical issues we were experiencing earlier have been resolved. Apologies for the inconvenience!

— Blizzard CS – The Americas (@BlizzardCS) August 23, 2016

The post Battle Net DDoS – 23 Aug 2016 appeared first on Arweth.

UPDATE 30th Dec 2015 (GMT): Valve have released a update to the issues that occurred on Christmas Day. The full article can be found here: http://store.steampowered.com/news/19852/

In short (TL;DR) Valve confirmed the issue was caused by a caching configuration change.

They have confirmed that the information displayed was read only and affected you only if you were logged into the store and accessing it at the time of the issue.

UPDATE 2:00AM GMT (26th Dec): Valve have release a statement regarding the breach:

Steam is back up and running without any known issues. As a result of a configuration change earlier today, a caching issue allowed some users to randomly see pages generated for other users for a period of less than an hour. This issue has since been resolved. We believe no unauthorized actions were allowed on accounts beyond the viewing of cached page information and no additional action is required by users.

This statement confirms the suspicions from SteamDB with the issue being with the content delivery systems configuration rather than a breach of security.

UPDATE 11:15PM GMT: Steam looks to be back up now and all looks correct now. No statement has been released by Valve at this stage as to the official cause of the issue.

UPDATE 10:06PM GMT: Steam look to have also taken down the steam client connections – The connection manager servers have been detected as offline around 10 minutes ago by https://steamstat.us

UPDATE 9:40PM GMT: Steam have shutdown the Steam Store presumably in response to this issue. This looks to have happened around 20 minutes ago by the the Steam status page.

Original Story: Today Steam have run into a major issue effecting the privacy of potentially thousands of Steam accounts around the world.

Users logged into Steam around an hour ago (8:30PM GMT on the 25 December 2015) were given access to other users account details when trying to browse the store. This revealed private account information such as billing details, purchase history, wallet balance and security settings on your account.

Steam Guard (Steams two factor authentication utility) does not appear to have protected your account in this instance as it appears the steam servers have got confused as to which connection should see what information.
This possibly could have been due to a caching issue on the Steam CDN (Content Distribution Network) as speculated by @SteamDB

It has been reported by a few users that purchases completed on the store have not been redeemed to their accounts and have presumably ended up in the account they were logged into at the time. This has not been confirmed by Valve at this stage.

As recommend by the SteamDB team do not log into your account until further notice even to try and check your account details or remove links to PayPal accounts. If you feel the need to make sure your account is secure please delink your PayPal account from Steam using the PayPal site. Instructions for this can be found here: http://www.wikihow.com/Cancel-a-Recurring-Payment-in-PayPal you can also contact your bank to cancel any credit / debit cards or put a temporary hold on the card.

If you have any information regarding this matter and wish to contact me flick me a message here, email me arweth@arweth.com or ping me on twitter @Arweth

The post Steam Security Issue (Winter Sale 2015) appeared first on Arweth.

This has been resolved now but may have been a security breach on the backend of the site.

I’ve made a few changes and added in some more security to the system to make it more secure.

Please note I have not been able to confirm that a breach has taken place but I want to be on the safe side. The site has also been thoroughly checked to ensure no malicious content is being served.

If you notice any issues or the new security measures cause issues please let me know.

Cheers,
Arweth

The post Site Issue appeared first on Arweth.

All content bar some external images are now loaded over HTTPS by default rather than standard HTTP.

Due to some issues with the HTTPS integration with the site this has been disabled. Maintenance will be scheduled in the future to resolve these.

If you locate any issues please let me know at arweth@arweth.com

The post Maintenance Complete appeared first on Arweth.

I expect the downtime to not take the full hour however.

Any changes or updates to this will be posted here.

The post Downtime appeared first on Arweth.

With this move I expect to see a massive performance boost as the server is faster but has also moved to a new location in the world that makes it slightly closer to me without reducing the performance of everyone else.

With this change I will be able to spend less time working on the back-end and will be able to spend more time creating new content for my sites.

I’ll be monitoring the website closely over the next few days and hopefully won’t need to take any further actions.

The post New Host appeared first on Arweth.

• Tabbed Chat
  Separate chat area’s are finally here. Tabbed chat will give you the option to have private messages appear in a separate area to global chat with the server. This will allow you to separate out conversations with different players into a separate tab.
• Admin Chat
  Along with the tabbed chat I will be bring in an admin chat system. This will let you chat directly to the other admins in a global admin chat or directly to an admin in a private message function
• Language and message customization
  You will now be able to customize almost any message the server provides automatically which also brings in the ability to enter messages in your own language.

Along with those main changes I am also making many changes to how the system runs in the background to make it more flexible and lees error prone.

I have also made the decision to open source CallAdmin and will be providing all the code on GitHub on the release of version 2.0

Unfortunately I’m not too sure when I will be able to release the next version at this stage I want to get it done ASAP but as a few of you who follow me on Twitter will already know my server failed so I’ve now replaced that but have had to reconfigure that from scratch as I lost all data on it at the time (I keep all CallAdmin code with multiple layers of backup so have not lost that). However what you won’t know is soon after I got the replacement server my computer’s main Hard Drive failed. I have since replaced this but I am currently in the process of gathering all my software and setting it back up again which is taking time.

Time-frame wise the new version should be available in around a month maybe two at the most. However I will try and work towards getting this done sooner rather than later.

The post CallAdmin 2.0 appeared first on Arweth.