 So I want to make a video because I want to cover some details about the unified system and some of the real world problems You ran into it. So demos are always great We want to see what challenges we face when we started deploying these now the challenges aren't huge There are more annoyances, but there's actually good work for these challenges and annoyances. So When you're looking at a lot of small business and VR systems You got to think about the fact that most of the clients want it persistently viewed on let's say a TV So we mounted some TVs for these now because like the one that I'm going to be showing you right here is a smaller system with only six cameras It didn't really make a lot of sense to have two Systems in there one to view and one to record. I mean, that's nice, but you can do it on one machine They don't recommend it, but you can be done as long as the machine is fast enough to do it it doesn't have a problem because Chrome can be a little bit burdensome running because One thing that they may not tell you about these unifies is viewing a lot of cameras requires a Faster processor to do not the recording of them I showed in my other video how little processing power is taken for the recording But there's a lot of processing power because it's all HTML 5 for the viewing But there's a few things you can do to fix some of the issues you ran into So on this camera system, this is the default live view now This is actually running on the same machine that's recording and it's working fine because the machine's specced for it It's a nicer i5 with a gigs ram which is plenty for recording six cameras with a Western digital purple drive Now we've been putting in separate boot drives versus the recording drive That way it boots up really fast off an SSD then records to the four terabyte drive Small SSDs to run Windows fairly inexpensive So the next thing we ran into was they wanted it to auto launch every time it rebooted Well, there's a solution for that and I'll post this little script in here We put in this little tool called unify dot VBS and what this does is on startup launches Chrome weights Then says go ahead and press center and that's because if you notice here, we have it set to 1 2 7 0 1 780 not 7 4 4 3 now the reason for setting it to that is because that is the non SSL port that you can view the unifies on Chrome has a hard time with self-sign certificates and one of the problems we're running into when it's using the SSL is When the stream changes Chrome will time out You'll actually still be viewing the cameras But it'll give a 404 error and I see a lot of people complaining about it And this is the easy solution around it if you're viewing it locally and it's like I said 1 2 7 0 1 780 and that is the port number slash live view what the script doesn't start up is Kicks off Chrome opens up the live view page now. You can there's a push keys or send keys for Typing in the username password. It's Chrome. It's local on this computer We went ahead and did the not recommended things so to speak in terms of security But we save the password in the browser of the nvr The reality is if you have physical access to the nvr and the password you've got everything Anyways because you're in the same room But so we have the username a password saved we wait a few seconds after this gives enough time to launch We wait and then we send the enter key to go ahead and log in and it defaults right to the live view Now challenges with the live view We're gonna go ahead here at live view and we're gonna edit the view now This helps a lot and I'll tell you it's it's a big problem that we didn't expect this client is a one-to-one So they have their one computer with one TV interviewing it Maybe another TV, but as it turns out with some of our other clients We're gonna click this here to low and we'll click in this little camera icon That's on each of these low low low And low but by doing this in lowering the streams here it one reduces the burden on there We didn't change what it records that we only changed What it was actually viewing at so on the view? It's now set to a lower stream because by default that actually sends the full stream over here And then switches back and forth as needed depending on that but by keeping the stream at full It was creating some real issues Because we have a client that has nine people watching your cameras and it turned out it was a bigger burden than expected to Do that and it was really taxing the machine It's even a machine that's dedicated for recording, but by doing this Lowering the stream on the view for each person that's logging in and viewing it reduced the burden on the machine It's funny that the cameras recording Were not too hard on the machine But once you have nine people watching the same system on a gigabit connection It didn't quite saturate the connection, but it really Did a big number on the processing power it takes to send those streams back out So we weren't sure you know why the client kept having problems And this is one with a dedicated server not this particular client But what solved the problem was changing that stream to be low So they can view it now they can change it back to high if they have one particular camera And I think there's a lot of excitement when we put all the we put like 30 cameras in for the client And there was a lot of excitement to watch all the cameras all the time now each department is only watching the cameras They care about and they've edited down to views and the problem kind of went away But it was kind of unexpected I just didn't realize that everyone wanted to watch all the camera streams at once And once you burdened the system with all the cameras recording and then all the people at their individual offices all viewing the cameras It really created some errors that were really hard to trace and a lot of them were out of memory errors Because of the streaming service going in and out getting burdened so much But between the VB script and then using a non SSL internal port That kind of solved it for us in terms of the troubleshooting we had I mean we were really worried about all the problems with it But that kind of sorted it out. We did notice on the windows machines They do perform better if you do things like turn off the volume shadow copy on the Larger drive Specifically the the West digital purple drive because we're booting off an SSD And then heading over to the purple drive. We turned off volume shadow copy And it's more risky, but you can turn off windows update as well seen as these machines are Signer and that avoids them randomly rebooting or you can just run this on a server Now it the program does start up by default But there's something you have to be concerned about if you do have it on make sure you have the reboot time scheduled To be less inconvenient because when Tuesday update day comes and the computer reboots on Wednesday because it loaded some updates Sometimes clients get a little upset. So make sure you are managing or thinking about that or do like we've been doing and a Lot of them we run Linux on them And it seems to solve some of the problems because we can control the update schedule on the Linux servers a little better So that's just my short video of little problems We found in easy ways to troubleshoot it use port 7080 internally or locally if you're viewing it on the same computer Think about how many people are going to watch it at once because I don't have an exact ratio But I will tell you it certainly Was a lot of bandwidth use and a lot of memory usage more than expected one all these people started watching it once The last thing is that VBScript, which I'll just go ahead and post the in in the comments here or in the description I'll post the VBScript that we use. It's really simple No big deal there So you can Copy that in put it in startup dot VBS and it launches chrome and logs in as long as you have the password It's saved you can enhance the script You can find a few people in the forum that did a few more things like typed in a username password all with a VBScript, but we found just saving it to be fine And the multiple stream issues set them all to low for the viewing you reduce the workload on the server You release a bandwidth necessary and it also will reduce the Processing power that chrome needs because one of the couple of users which I guess it's not horrible It led to some computer upgrades for us They were trying to view it on really old computers that they had and it turns out that it doesn't render well on like You know nine-year-old computers that they probably should have replaced anyways But they were using for basic needs but watching cameras on there. You do need a faster computer I do recommend just for the viewing portion being an i5 system It actually takes more horsepower to view the cameras and it does for the system to record them So that was it. That was my quick unify update that I wanted to cover Other than that we're really liking the systems once we got those little issues sorted out Also, by the way, if you're running into the cameras being unmanaged in some of those issues it's all related to that all those problems went away by Fixing these issues it stopped all the other errors that was like cameras timing out and stuff like that Well as it runs out of memory, it does random things It doesn't necessarily tell you unless you're looking for out of memory It does random things like tell you that cameras unmanaged or that cameras decided to turn off and you thinking you're having camera problem Nope, it's all related to the nvr in a workload on it So thanks for watching like to continue like a scribe you have questions comments Let me know and hopefully this helps you solve some of the unified problems if you're ever seeing the same ones we are. Thanks