Back to Blog
Sepm 147/8/2023 ![]() I did wonder if there would be an issue with moving the drives between the T320 & T420 units. This week when I came to log into SEPM 14.3 I encountered " Unexpected server error". These are of course still linked to SEPM 12.1.5 on the windows 7 PC. I then concentrated on configuring workstations ready for users this week. I updated the Windows key and successfully telephone activated. Just before Christmas I moved these two drives to the main T420 server that also has the shared data drives. ![]() I installed SEPM 14.3 with no obvious issues and could manage two client workstations. With the first pair of drives fitted I installed the OS then migrated the domain from the previous server. Initially 8GB was installed but currently also 16GB. I have fitted several memory modules for testing. The CPU is the same family just 4 core rather than 6 core. This is a Dell T320 which is essentially the same, just a single CPU socket and supporting chipset. All workstation applications are local, not installed and shared from the server.įor development and trials I have a second server. The local intranet is run on a separate Windows 7 PC. The server is the domain controller, user manager and print server only. The second pair are the shared data files. One pair has the OS plus in a second partition the support and installation packages e.g. There are two pairs of drives in RAID 1 (mirror) configuration. This is a Dell T420 with single CPU and 16GB RAM. The Endpoint 12.1.5 SEPM is running on a Windows 7 PC. ![]() A key reason is Endpoint 12.1 being unsupported from April. The background is I am upgrading a small totally offline network. However at all times the NIC has been present as integral to the motherboard. I am using the full package Symantec Endpoint 14.3.0.1 MP1 Refresh. I need to know the cause(s) and solution(s) to repeatedly getting "Unexpected server error" when attempting to log into SEPM 14.3. ![]()
0 Comments
Read More
Leave a Reply. |