window| E-commerce | design | Scaling in this case, we'll change it to a more secure setting-24. Now, if you're smart and you've set up your stats strategy, get your keys changed every 42 days instead of 30 days, because 30 days will let the hacker know exactly when your key changes. So set a random number between the two. So we say 42 days.
If you remember 24 keys, that's after three or one-second years. That's a good key list. Note that this will precisely define the policies in the database. I click okay then you notice under the database settings, will tell you that 24 keys are memorized and the computer settings are passwords Remember, now enforce password history no longer have red tags.
Now look at some of our other nodes and we'll look through and set up the event logs, and you'll notice that I clicked my settings for event log. In this example, I will click on my audit policy and extend my system node, which shows us all the services to be protected; Extend my file system nodes, which will allow me to protect any folder or any object, as we have been able to do.
Instead of doing it in a random way, in a variety of ways, now you can do it like a separate section in the admin console. The interesting point is that since you can do it in one place, there's no reason to continue to have a loose security policy.
What we're going to do now is to look at our key again and look at the maximum key age. Recall that we discussed the key age. We've set it to 42 days and that's good. Double-click it and make the changes, now let's set it back to 31 days. Note that 31 days is a database setting, but the computer settings are still 42 days
Note that those are in the direct content and that is why the Red Fork is now displayed. Our minimum key length is now set to zero, which is not very good. We don't want an empty key so we change it to 8 because 8 is a good loop number. You can set it to any number of wishes. Once again, we click on Okey and what is really important now is that we will click on the completely appropriate key.
This means that your key must now be a combination of numbers or symbols without uppercase or lowercase letters. By creating this particular requirement, you've increased the amount of time that a hacker might break your key with log crack or something like that, and then we click Enable and then click Okey.
Then, given this limitation, some users will choose a key such as FRIDAY13. When the key expires, they cannot be used again because we have set Windows 2000 to remember the old key so what we have to do is we set it to be more difficult.
It is also possible to lock our admin account if the administrator has typed this key too often. As a security feature, an administrator can log on locally, even if your account is locked.
So finally, to close the final security loop, we have to enter the account lockout and activate the lockout threshold. Then the account will not lock, we will change to 3.
Please pay attention to what I have done immediately, this dialog box changed to count will be locked after I click Okey. Note that the setting for the next item will be changed automatically because the value is 3. So, automatically, it will request us to reset the account lockout counter after we enter, and it defaults to 30 minutes.
We go in and change it to the appropriate value, that is, 9,999. What does that do? Well, that effectively means it's never been reset. The advantage of this is that it cannot be reset without the administrator.
Now, once you've checked and set them up carefully, you'll notice that you're already in the competition. All you have to do again is analyze your system again based on your new settings. All you have to do now is set up your computer and set up your database as well.
In this demo, you learned how to install the Security configuration and the analysis console in the Microsoft Management Console. The first time you learned how to create a security database and configure your system. You learned how to analyze your system and use a security template and ultimately learn how to modify them to fit your best security settings, then come back and analyze them based on your new changes.
Now let's go back to PowerPoint slides and get into some of the best practices.
OK, now let's go back to PowerPoint slides and analyze your URL traffic. We have protected our system. We have optimized our system. We have moved on and emphasized our system. The last thing we need to do is analyze our web site traffic to get it working correctly.
When analyzing your Web site traffic, ask yourself questions about where your users are from, what kind of ads work, what they like, what your most popular pages are, and how often you average conversations.
The next issue is decision support. In order to analyze the user's common string, you need to know what the Web page is intended for. They are hit and unique hits, destination pages, directories, subdirectories, domains, URLs, services, and all network information to be set beforehand.
What are your reference pages, domains, Web addresses, services, or networks? What is your top page to be accessed and referenced? What browsers and operating systems do people use to access your Web site? That will change the way you run your program. When is the peak visit time of your every page? Summarize strategies for specific pages or URLs you can do these things on a daily or monthly basis, or at some point in hours.
Now let's go to Demo 4, which is about how to analyze your URL traffic. We are now moving to the demo screen. In order to analyze your Web site traffic, we will use the URL Server Analysis tool suite, in order to start using it, we want to create a database for this analysis tool.
So you have to install the summary server to complete. And, here, we're going to use sequel Server 7.0. It's a better analysis tool and there are overlapping services that we'll use in future demos. You have to have administrative authority, that's very important.
When your database setup is complete, we will use the use Input tool to bring your existing records into the new database. So we will go to the URL server and then analyze and from there we open the use introduction.
Once you are in the use Introduction tool, you will be asked a series of questions to move the record information forward into a specific database on a particular Internet site. We will ask these questions when we pass.
So we saw that the introduction manager appeared and in our introduction manager, we went forward and browsed our record data. The record data we want to use is in a folder called Usage Analysis Plus and can be used in the Resources section. We will use UA underscore Plus,underscore Sample.log then we will click Open. That will put the log file path into the Record path field and we will add it to our list, and then add that path and record to our list that will be introduced.
Note Now that I'm going to go out and click Browse and get more records from different places, that will allow us to now gather records from different servers if we want to do so. Now we click on import that will bring all of our records into the data structure, which we have created for the database. The data structure that will be used is sequel Server 7.0. This database is created when you start to use analysis. The analysis tool, one option is to create a database, to do with a specific pattern to create the database so your section will have like hit, visit, request that thing.
The message now is to introduce our record data into a specific pattern and populate it with information. What we're going to do, what I'm going to show you is-the database settings, right there, I'm going to use the introduction of the use. We have basically completed the introduction here.
All your time will be used for the introduction of the work. It usually doesn't consume a lot of time. Well, the introduction of the work has been done. It used to 1分钟36秒, which was quite long for me.
I'm going to click on Okey and then we get a good announcement here that tells us that the introduction has been done; and how many requests have been introduced. Note that we have introduced more than 11,000 requests, which are rare. There is a parce error, which is not very large, which tells us that the data has been introduced and time-consuming 1分钟36秒.
That's actually what we use to introduce. Let's go ahead and close it. To what we really want to use, at that time our reporting tool. That is, of course, in the URL server analysis is then in the report logger.
In this notification logger, we will get these records that have been entered into the database and will produce some reports. First, we will produce a encapsulated report and we are going to use an already established report. Then we will build our own report from there.
In a future demo, we'll continue and use an add-on to the UA Plus to actually create a report that uses OLAP Services. Here we click on Okey. Then pull up the report logger directory we're looking at here.
In the report logger directory, there are detailed ad reports for those who have ad revenue. There is also an intranet report, if you want to use your system for an intranet; a Web server report; and, here, we're going to look at our summary report and the Management summary report.
Now, the report manual tells us a little about its scope and I'm going to click on the next tab. I'll just leave this setup but we can finish and adjust it to a specific data range or last three days or last day, and so on.
Notice that it asked me for a report name. I call it a summary report and then note that the output format is HTML. I clicked Okey. That output format, by the way, does not have to be HTML. can also be for other output formats.
In this example, all the data put into the structure is dragged into the report and a HTML folder based on that kind of reporting information is generated. In this summary report, we will find an overview of your Web site statistics.
Management summary, which will be shown for example daily access tendency, geographical area, daily use. It also displays browser information, which is now in our record data, only IE so that will be minimized. But in a real world position, that would be a very meaningful test.
Here's my summary report now created in HTML and we'll roll it down, and you'll notice that I have content to show if I click on that link that will take me to the daily access trend. It's just a day. If I click on the user organization and geography here, I get more charts and here is the form of my picture. Above, I have the top 20 requests, the number of requests, and the percentage of requests.
Here is a very good management style summary. And then one thing I really like about it is, at the bottom of it, there's the definition of a standard Internet item so that if you distribute it as part of your package to advertisers and so on, then you'll have a standard definition of what you can work on.
That's a good report, except for the length of the system when you create a report from the draft so I'll go ahead and close my admin summary report, and then I'll click New. New brings up the calculation list, which is a very detailed calculation based on a URL.
I like it because it now allows me to browse and build my report, only by dragging and dropping parts. But what I'm going to talk about is creating this report from the full draft. So, I'm going to create a new calculation by right-clicking my account definition and saying the new calculation.
Now in my new calculation, I'll browse and right-click my row dimension. and select the new dimension. So the calculation will be on the line of this dimension, and then the row of the dimension will be in the Content section, in the request section, then in the title, and this is at the bottom. then click Okey. Now it's down there.
Then I'm going to click the Details tab for it and then go back to properties. and its details label. And then, in this case, I'm going to turn it into a finite result. Note that I can categorize them by dimension or by summarizing other summaries. But I'm going to leave it like this. I clicked Okey.
Now I'm going to right click on my metrics and choose the new metrics. And then, in this case, I'm going to go ahead and that's my metric. I will make some requests now. In my detail tag, I will continue and display the value as a percentage of the column. Then I click on Okey.
So, now the display is a title and a 1% request. I'm going to add another metric and do the same thing but I'm going to say the number of requests. I want to make sure I show all the requests and then come to details and click Okay. And then it was done.
Now, I'm going to run this report. Now that I've set it up, I'm going to run it and, again, I'm going to give it a file name. This one, I'm going to pull the hit number because what I expect is the number of hits per page, based on the percentage of all hits. I'm going to create it now.
Here is the number of requests that are then my sample address the number of requests per page hundred points
