foreign this is Daniel Slocum I am an I.T Asset Management technical practice director here at Glide fast and I want to talk to you today about the new guided setup in the Vancouver release of servicenow for SQL Server this is part of the Sam Vancouver release showing you the servicenow Vancouver release notes product documentation and I wanted to just guide you to where you can find the information so under Vancouver release notes scrolling then down to learn about the Vancouver release release notes for upgrading from Utah or not any of the other versions features and changes by product and then underneath it Asset Management release nodes you'll see software Asset Management release notes once you click on that you'll have the menu that's in front of you the screen and scroll down from the top software Asset Management release notes down into the new in the Vancouver release and the manage Microsoft server licensing through guided setup is what we're going to be talking about today so I'll just click into it but I don't tend to walk through it in the documentation you can read that on your own I'm going to pop into a Vancouver instance currently I'm starting from the Reclamation rules and I'm going to drop into the workspaces now why am I on Reclamation rules and there's no reason except that I wanted to show you something about workspaces if you're not familiar with them and that is when you access the software asset workspace it will automatically drop you into the area of the workspace that you were working in last in this case I was in the success portal so it dropped me into the success portal the SQL Server guided setup can be found not there but under home got it set up so you click on guided setup and you see Microsoft SQL Server license management guided setup there are playbooks in software Asset Management that you can access from the success portal but the guided setup right now is limited to Microsoft SQL Server so the first thing that it presents you with are the prerequisites I'm going to click edit so you can actually see these I've already stepped through some of them so the first thing here on the left you can see that there are three different listings of instructions for the guided setup prerequisite software Asset Management configurations and then verify the software Asset Management configurations we start with prerequisites and it has the list of things that you need to accomplish here under prerequisite so the first one is install software Asset Management publisher for Microsoft plugin if you do not have the publisher pack for Microsoft this is the time to install it I have it installed so the market is complete the next one here let me click edit again the install the itam health check application and you can see it's showing as active the description verify the software Asset Management configuration so the health check is also installed moving on the next step is to validate the servicenow discovery is installed I'm not going to actually click into each of these now you get the drill do you want to make sure that they're active and this is a little grayed out but it's showing active I actually had to install this in this instance this demo instance to get it to be active but you're you will most likely have this already active in your environment if you're a servicenow discovery customer install the latest Discovery and service mapping patterns so this can be found in the servicenow store it is a free plugin that you can add on at any point and you can download it and install it directly from the servicenow store or you can navigate to it from the plugin section and search for it inside of your instance and it will connect to the servicenow store and download the details so then the last step is to actually run a health check on SQL Server cmdb configurations now why would you want to do this at the start well you need to get a baseline so the first thing you do is you go into the software asset success portal run a scan on SQL Server cmdb so I've done that but I will show you where that is so in success portal we execute a scan and then we choose from the list of scans that are available we want to run it on SQL Server cmdb so execute this really doesn't take terribly long it checks some tables some configurations and checks a few other things so let's click on view results so it has a listing of things here that it's looking for 246 to be exact it's checking tables it's looking for different software installations it's looking for entitlements and a number of other things so the checks here we are we have eight different checks one of them is critical and then it checks the SQL Server Suite so this is not a conversation about how to read scans and how to take action on scans this is a conversation about the guided setup so we'll move back to the guided setup now so we've run the initial scan so we will then go back to the guided setup and we will click on prerequisites and move on to software Asset Management configurations and so here we want to verify that the SQL Server is set up and it gives us some instructions click edit so we can see those if you're setting a Microsoft SQL server for the first time best approach is to create entitlements and software models using publisher part numbers if you've already set it up the best approach is to delete and retire the existing software entitlements and models and then they want you to create entitlements and software models using the publisher part numbers now why is that important it's important because the publisher part numbers will automatically create the correct models with the correct configurations when you enter them as an attribute on a software entitlement record it'll also add additional data such as the discovery map it will add end of life and of support and other lifecycle data and it will it will set you up for Success now here if you click into these links it's going to take you directly to a software entitlements for SQL server and then of course it'll take you to the SQL Server software models and these were created as demo data in this instance I did not actually go through and create software entitlements using publisher part numbers but that is what you want to do and these links will show that they are done so this step make sure that you create your software entitlements and your software models using the publisher part numbers on a software entitlement record we're going to mark this one complete click continue now the next step is to look at software installation conditions for Microsoft SQL Server that apply to all SQL Server software models what is this about well this is leveraging something that's been in Sam since the Jakarta released when was first released as in service now and that is you have software installation conditions on your software model that can preclude reconciliation from taking account of installations on a specific device based on the condition that you specify so what does that mean for SQL Server well if you have SQL Server installed in an environment say a test environment or a a lab and your contract your terms and conditions allow for those to be present without consuming a license then this product install condition on the software model will make sure that you don't and I believe there's also a product install condition table now for SQL Server product install conditions and you can click new and create those as well so we're going to mark this as complete click continue and then the next step we're going to step through the different components of the SQL Server Suite in that in this case the visual studio product install conditions launch me Microsoft SQL development install condition setup so we're going to set up install conditions for SQL Server Developer Edition which typically is not licensed SQL Server Express Edition which would be licensed most commonly with an application that leverages SQL Server Express and then SQL Server disaster recovery so all of these are steps that you need to work through as you install and set up your environment for Echo SQL server and then the last step is to verify SQL Server Asset Management configurations and it wants you to then run the guided setup excuse me run the health check again and compare then your results from the second execution to the first execution and then the next step would be to create a success goal so the success portal was created to allow you to track your goals and your goals then would be goals that lead you to Roi so creating a success goal for incrementally increasing your effectiveness at managing SQL server or anything else those would be you know Reclamation rules and those would be creating other tangible activities or experiences in the product that allow you to realize Roi be it real Roi from is cost savings or cost avoidance or tangible but more nuanced rois such as efficiency gains for employees that are doing things faster because of cm and then the last piece of course you want to run reconciliation see how well you have accomplished your goals and achieving compliance with Microsoft SQL Server so there you have it Microsoft SQL Server license management guided setup in the Vancouver release [Music] thank you [Music] foreign