WEBVTT 00:06.100 --> 00:10.750 In this lesson, I want to talk about TASC servers, and before I do that, I do want to talk a little 00:10.750 --> 00:15.940 bit about some options for running the Apple remote desktop without having to configure a machine to 00:15.940 --> 00:18.050 be a test server for you on. 00:18.100 --> 00:24.010 One of the more common things I've seen and works pretty well is to set up a Mac server or set up a 00:24.010 --> 00:30.580 Mac client with a static IP address on the network at a particular campus or office building or whatever 00:30.580 --> 00:31.840 the situation calls for. 00:32.350 --> 00:36.670 And you'd simply do that by going to System Preferences Network. 00:38.200 --> 00:39.190 Go to advanced. 00:40.170 --> 00:47.100 TCP, IP, and then here you can manually identify manually set your IP address here, so if you have 00:47.100 --> 00:53.610 a static IP, set your machine, you know that you can then add that machine to an Apple remote desktop 00:53.610 --> 01:00.660 session or you screen sharing built into OS 10 from a client machine to get to that Mac server or Mac 01:00.660 --> 01:06.020 client wherever and wherever you happen to be, and then be able to launch remote desktop. 01:06.120 --> 01:12.780 Now, if you're going to use remote desktop to use to remote into a machine that will also be using 01:12.780 --> 01:16.310 remote desktop, there is one very important setting you need to set. 01:16.330 --> 01:21.780 Otherwise you can get into this catch twenty two where you may not be able to actually launch remote 01:21.780 --> 01:27.360 desktop on that remote machine through with remote desktop sharing turned on. 01:27.480 --> 01:34.320 So you need to do there is going to preferences on remote desktop, go to security and then check this 01:34.320 --> 01:38.220 box, allow control of this computer when this application is running. 01:38.770 --> 01:45.870 If you have that turned on, that will allow you to remote a computer with remote desktop and then launch 01:45.870 --> 01:49.320 remote desktop on that remote computer and interact with it. 01:51.030 --> 01:57.270 Let's say you decide, instead of doing that, you'd rather just have one client on the network set 01:57.270 --> 02:01.560 up to be your remote desktop task server. 02:02.270 --> 02:08.580 I can figure this, you have to do a couple of things first, you have to go into and I would recommend 02:08.790 --> 02:12.250 setting up that static IP address on whatever machine that's going to be. 02:12.480 --> 02:18.810 So this should be ideally a computer like in the data closet that no one uses that's there for maybe 02:18.990 --> 02:21.690 maybe it serves some other functions, runs other services. 02:22.110 --> 02:28.410 But it should primarily be something that people aren't using day in and day out for regular work. 02:28.410 --> 02:32.050 So don't have it be your boss's laptop or something like that. 02:32.070 --> 02:37.170 It should be a desktop machine, preferably hard wired, preferably with a static IP address that. 02:38.500 --> 02:45.850 Two, it should have remote management turned off, so if you remember when we were setting up the client, 02:45.850 --> 02:48.580 we went into sharing and we had remote management turned on. 02:48.580 --> 02:51.430 You're going to want to make sure that's turned off on the machine. 02:51.430 --> 02:53.560 That is going to be your test server. 02:54.400 --> 03:00.010 Now, the reason for that is that I have found, at least in Mojave, having that turned on or having 03:00.010 --> 03:07.360 the remote desktop application running when you're trying to connect to it as a test server causes remote 03:07.360 --> 03:08.230 desktop to crash. 03:08.510 --> 03:10.730 So your results may vary. 03:10.990 --> 03:11.940 I've been doing that. 03:12.130 --> 03:12.890 Just be safe. 03:14.240 --> 03:21.380 Two or three, rather, you go into system preferences on the machine that will be your task server 03:21.650 --> 03:24.020 after you've installed remote desktop, launch it. 03:25.110 --> 03:32.370 Go in to preferences, go to task server, and it'll have this automatically turned on, but you want 03:32.370 --> 03:35.520 to check the box for allow remote connections to the server. 03:36.180 --> 03:42.180 Once you've done that, you basically set it up as a test server and then what you can do. 03:43.300 --> 03:48.520 Is close out a remote desktop, and now it'll run as a service in the background, if you have a remote 03:48.520 --> 03:54.370 desktop running, if you have remote management turned on in system preferences, when you go to any 03:54.370 --> 03:59.770 other machine running remote desktop and you want to connect it to the test server, you will have a 03:59.770 --> 04:03.730 problem because the application will repeatedly crash, at least in Mojave. 04:04.580 --> 04:11.180 Now that I've set up the task server to function as a remote desktop server, I do need to go to one 04:11.180 --> 04:17.600 of my other remote desktop machines and here I am back on my administration machine and I need to go 04:17.600 --> 04:22.100 ahead and set this one up to use that new test server that I just configured. 04:22.100 --> 04:27.320 So to do that, I just launched a remote desktop, as I have here, and I go up to the system or to 04:27.320 --> 04:31.730 the preferences for remote desktop and I go to the test server tab. 04:32.150 --> 04:37.880 And instead of by default using the test server on this computer, I'm going to choose to use a remote 04:37.880 --> 04:38.690 task server. 04:39.020 --> 04:43.040 And that's where I can put in the IP address of that remote server. 04:48.940 --> 04:50.290 And select. 04:51.110 --> 04:57.170 And it'll validate the test server, and once it does that, I will be able to schedule jobs and the 04:57.170 --> 05:00.250 test server will handle scheduling those jobs instead.