Now we've determined what our issue is. We've tested our theory. We've implemented our we've implemented our solution. We've put in place our plan of action. Next, we want to verify our full system functionality and perform any preventive maintenance procedures that we may need to d'oh. So when
once we've put in place are potential solution? We don't want to just say, Okay, we're good and hand back of the computer to the person that's using it or just walk away. We need to make sure that the computer does work, not just with the exact the exact
programs or the exact performance that the person was trying to use the user was trying to use when the issue occurred. But also we want to check some other settings to make sure that changes we've made has an effective other system. Settings hasn't made them lose their Internet connection or made them lose some files or lose the ability to open some files.
their system functionality, make sure their whole system is good and we didn't make any changes or we didn't miss anything that might have been a recurring issue,
so it's good to perform the actions that occurred before or when the issue occurred. Unless, of course, they're the actions that caused the issue. We don't want to. If someone has a computer screen that's cracked because they're dropped their computer down the stairs, we don't want to verify the system functionality by dropping the computer down the stairs again. Um,
we want to perform the actions. If they're things that may have led up to the issue like someone's trying,
Thio may lead them to realize the issue like someone was trying to send an email and their email service crashed or they were trying to connect to the Internet and navigate to this particular website, and the Internet wasn't up. We want to make sure that we have them try to send a test test email and it's good. Okay, that's great,
or we want them to not only make sure that they have Internet
and that they can get online, but they can get to the website the resource that they were trying to access before. Maybe they try to access that resource and they still can't access it. We do a little bit more digging, and we determine that it's not their intimate connection that was really at fault. But it's there. The browser isn't the correct isn't updated enough for them to access this Web page.
Or maybe they don't have the correct credentials or they're smart. Card isn't working, so they can't access this resource.
So we need to make sure that we verify that we perform those actions, that the user is able to do exactly what they were trying to do when they noticed the issue.
If possible, we want to follow up later. Following up later will allow us to make sure that the issue hasn't rickard make sure that it hasn't caused any other issues and maybe do a little bit of tweaking or perform some preventive maintenance per sheet procedures. Now, preventive measures are things that include
installing anti virus programs, blowing dust out of the computer, setting up windows automatic updates, automatically patching programs, just cleaning cleaning keyboards if they were sticking, making sure that cable's air managed different preventive maintenance procedures that help prevent
this same issue or even other issues from occurring.
This is all part of the preventive maintenance procedures are part of verifying the full system functionality and it's fought part of the following up that we want to do when we have users that are experiencing issues.