We just recently began supporting a 2008 server and can't seem to wrap our heads around this error that's causing the server to reboot every 7 days. Logs show that it is out of license compliance, but nothing we find validates this. WGA passed, it is the only server in the building, there are no trusts, there are 6 users. I thought about just disabling the Server infrastructure License service but didn't know the effects of this. Below are the related events I found. Has anyone seen anything like it before?Windows Server Standard FE SP1Thank you for any input!KennyID 38: The External Licensing Enforcement Load Checks detected a condition in your environment that is out of compliance with the licensing policy. This server will be automatically shut down if the issue is not corrected in 2 day(s) 23 hour(s) 0 minute(s). Please look for additional events for External Licensing Enforcement Load Checks to troubleshoot.ID 10: The licensing enforcement service could not load external checks because error code 0x80092003 occurred in function f1100.An error occurred while reading or writing to a file. This server will automatically shut down if the external checks cannot be loaded. Refer to the product documentation on licensing for additional information.ID 13: Domain Controller Check passed.

Any thoughts?

his error occurs when the server cannot finish checking the requirements for the root domain, forest trust configuration, or both. It usually happens when the server cannot connect to a domain controller. Sometimes this error occurs intermittently—if you close the error message and it does not recur within two hours, the problem is resolved. However, if the situation persists, the server will shut down 10 days after the first time the compliance check failed. Each time this error message occurs, it will state the actual time remaining before the server will shut down. If you restart the server after is has shut down because of noncompliance, the server will shut itself down again in 3 days. Link http://technet.microsoft.com/en-us/library/ee526849(WS.10).aspx Ramon Ant. Morillo Morillo MCITP: Enterprise Administrator Windows Server 2008 MCITP: Enterprise Messaging Administrator Microsoft Exchange 2007

In case anyone has this problem, this is because Windows Essential Business Server 2008 known as Windows Server 2008 for Windows Essential Server Solutions (WinWESS) (also known as Windows Server 2008 Standard FE) needs you to configure WinWESS CAL licensing manually (Unlike Server 2008 standard which goes by the "honor system"). There's multiple naming conventions for the "essential" variations of "Windows SBS Server 2008"; It does make troubleshooting and finding KB solutions harder, because you assume Windows Server 2008 tools and solutions are consistent across the products, but it's not. Under my WinWESS server for example, the "Windows Essential Business Server Administration Console" feature was comnpletely missing. I only had server manager. YMMV of course. http://technet.microsoft.com/en-us/library/dd279492(v=ws.10).aspx Steps To Prevent WinWESS Server from shutting down automatically due to CAL licensing [Caused by Error ID38: Failure of External licensing checks and Error ID 10: Failure of licensing enforcement to read/write to a file]: PREFACE: Do these steps after normal business hours, because you must assign CALS after "step 2". Otherwise your domain users will get the Your account is configured to prevent you from using this computer. Please use another computer. error message when they logon. To enable the user to log on, you MUST assign a CAL to the user account (per user) or the computer (per device): (Get ready for some fun, I wasn't expecting to be a CLICommandGod(TM) to use "Windows Server 2008 for Windows Essential Server Solutions" Follow the 3 steps below, and this will allow WinWESS CAL licensing to work properly. Step 1: install Windows PowerShell (during the install it appears to hang, but actually takes awhile to install, give it time to finish) On the desktop, click Start, click Administrative Tools, and then click Server Manager.At the User Account Control prompt, click Continue.In the Server Manager dialog box, in the console pane, click Features.In the Features pane, click Add Features.In the Features list, select Windows PowerShell, and then click Next.On the Confirmation page, click Install.When the installation is finished, click Close. Step 2: Install client access licensing Insert the WinWESS DVD, and then, on the desktop, click Start, click All Programs, and then click Accessories. Right-click Command Prompt, and then click Run as administrator.At the command prompt, type msiexec /i G:\tools\licensing\WinSB.msi /qn and then press ENTER. (Assuming G is the DVD drive letter where you inserted the WinWESS DVD. Wait a few minutes for this step to complete)At the command prompt, type cd C:\Windows\system32 and then press ENTER. (C is the drive where you installed WinWESS.)At the command prompt, type LicensingSetupForWinSB.cmd and then press ENTER. (This step should go fairly quickly) Now verify by checking server event ID#31 logs: Go to server manager>diagnostics>Event Viewer>Applications and services logs>Microsoft>Windows>Server Infrastructure Licensing>OperationalLook for event ID#31, it should say "The external licensing enforcement check passed.". If it does, give yourself a high five, now it's not shutting itself off in "x" days/hours due to failed licensing compliance checks. Hooray! (OK Step 3 is REALLY important, you must now assign CALS "per device/computer" or "per user" before normal business hours or the domain users will get: Your account is configured to prevent you from using this computer. Please use another computer. Isn't that great? (After reading both URL's, realizing EBS Administration Console gui is completely missing on WinWESS server, and further frying my brain, I combined the steps and came up with the 8 step method) my original sources: http://blogs.technet.com/b/essentialbusinessserver/archive/2009/10/12/understanding-ebs-client-licensing.aspx; http://technet.microsoft.com/en-us/library/dd252607(v=ws.10).aspx Step 3: View CAL summary, Assign CALs via PowerScript, View CAL Assignments Click the start button>all programs>administrative tools, find and right click "run as administrator" the shortcut labeled "windows powershell modules" (you'll get a message saying powershell is disabled due to server policy, just ignore)In the same Windows PowerShell window, type Set-ExecutionPolicy RemoteSigned, and then press ENTER. (powershell commands are now enabled). Now download the file located here or you can go to this site and manually download it: https://skydrive.live.com/?cid=d5fe25afb6c3615f&id=D5FE25AFB6C3615F%21136 look for file "bulkassigncals.ps1"IMPORTANT! before running the CAL assignment powershell script, go to active directory and delete/disable any old domain user accounts, test domain user accounts, or accounts from people that left the company, so the script won't assign CALS to them.In the same Windows PowerShell window, CD into the directory where you downloaded the "bulkassigncals.ps1" fileIn the same Windows PowerShell window, type this command .\bulkassignCALs.ps1 standard and hit ENTER (yes that is a ".\" in front with no space). If you have the premium edition, replace the syntax word "standard" with "premium"). The script will now assign CALS to every domain user account [without a CAL] as "Per User CAL".In the same Windows PowerShell window, type this command gcm -type cmdlet | ? {$_.PSSnapin.Name -eq "Microsoft.BusinessServer.Licensing.PowerShell"} and press ENTERYou will see some CAL powershell commands. Use "Get-CalSummary" to view a summary of your installed CALS. Use "Get-CalAssignment" to view the current CAL assignments. IMPORTANT NOTE: When you add, change,or delete domain user accounts, remember to rerun step#6 so it can assign or free-up CALs accordingly IMPORTANT NOTE#2: There are 2 CALs reserved for the server's computername (per device CAL) and Administrator (per user CAL). These special CALs do not count against your normal CAL allocation. Do not attempt to manually re-assign CALs from these 2 accounts. Example if your server comes with 5 cals, you will actually see 7 CALS total when you do "get-calsummary" in powershell (since 2 are reserved) Name Category Object Type Edition NameOfYourSBSServer Built-in Device standard or premium Administrator Regular User standard or premium Well I hoped you had fun as I did. Next time I plan to stick to "Windows Server 20xx Standard" in the future. Had I known CALS were handled differently under "Windows SBS essential server" products, I would have thought twice. YMMV of course. I will continue to update this solution as needed.

In case anyone has this problem, this is because Small Business Server 2008 and Essential Business Server 2008, known as Windows Server 2008 for Windows Essential Server Solutions (WinWESS) (also known as Windows Server 2008 Standard FE) needs you to configure WinWESS CAL licensing manually (Unlike Server 2008 standard which goes by the "honor system"). Ain't it great there's so many naming conventions for basically "Windows SBS Server 2008? Makes troubleshooting and finding KB solutions easy right? #sarcasm http://technet.microsoft.com/en-us/library/dd279492(v=ws.10).aspx PREFACE: Do these steps after normal business hours, because you must assign CALS after "step 2". Otherwise your domain users will get the Your account is configured to prevent you from using this computer. Please use another computer. error message when they logon. To enable the user to log on, you MUST assign a CAL to the user account (per user) or the computer (per device): (Get ready for some fun, I wasn't expecting to be a CLICommandGod(TM) to use "Windows Server 2008 for Windows Essential Server Solutions" Follow the 3 steps below, and this will allow WinWESS CAL licensing to work properly. Step 1: install Windows PowerShell (during the install it appears to hang, but actually takes awhile to install, give it time to finish) On the desktop, click Start, click Administrative Tools, and then click Server Manager.At the User Account Control prompt, click Continue.In the Server Manager dialog box, in the console pane, click Features.In the Features pane, click Add Features.In the Features list, select Windows PowerShell, and then click Next.On the Confirmation page, click Install.When the installation is finished, click Close. Step 2: Install client access licensing Insert the WinWESS DVD, and then, on the desktop, click Start, click All Programs, and then click Accessories. Right-click Command Prompt, and then click Run as administrator.At the command prompt, type msiexec /i G:\tools\licensing\WinSB.msi /qn and then press ENTER. (Assuming G is the DVD drive letter where you inserted the WinWESS DVD. Wait a few minutes for this step to complete)At the command prompt, type cd C:\Windows\system32 and then press ENTER. (C is the drive where you installed WinWESS.)At the command prompt, type LicensingSetupForWinSB.cmd and then press ENTER. (This step should go fairly quickly) Now verify by checking server event ID#31 logs: Go to server manager>diagnostics>Event Viewer>Applications and services logs>Microsoft>Windows>Server Infrastructure Licensing>OperationalLook for event ID#31, it should say "The external licensing enforcement check passed.". If it does, give yourself a high five, now it's not shutting itself off in "x" days/hours due to failed licensing compliance checks. Hooray! (OK Step 3 is REALLY important, you must now assign CALS "per device/computer" or "per user" before normal business hours or the domain users will get: Your account is configured to prevent you from using this computer. Please use another computer. Isn't that great? (After reading both URL's, realizing EBS Administration Console gui is completely crippled or missing on my server, and further frying my brain, I combined the steps and came up with the 8 step method) my original sources: http://blogs.technet.com/b/essentialbusinessserver/archive/2009/10/12/understanding-ebs-client-licensing.aspx; http://technet.microsoft.com/en-us/library/dd252607(v=ws.10).aspx Step 3: View CAL summary, Assign CALs via PowerScript, View CAL Assignments Click the start button>all programs>administrative tools, find and right click "run as administrator" the shortcut labeled "windows powershell modules" (you'll get a message saying powershell is disabled due to server policy, just ignore)In the same Windows PowerShell window, type Set-ExecutionPolicy RemoteSigned, and then press ENTER. (powershell commands are now enabled). Now download the file located here or you can go to this site and manually download it: https://skydrive.live.com/?cid=d5fe25afb6c3615f&id=D5FE25AFB6C3615F%21136 look for file "bulkassigncals.ps1"IMPORTANT! before running the CAL assignment powershell script, go to active directory and delete/disable any old domain user accounts, test domain user accounts, or accounts from people that left the company, so the script won't assign CALS to them.In the same Windows PowerShell window, CD into the directory where you downloaded the "bulkassigncals.ps1" fileIn the same Windows PowerShell window, type this command .\bulkassignCALs.ps1 standard and hit ENTER (yes that is a ".\" in front with no space). If you have the premium edition, replace the syntax word "standard" with "premium"). The script will now assign CALS to every domain user account [without a CAL] as "Per User CAL".In the same Windows PowerShell window, type this command gcm -type cmdlet | ? {$_.PSSnapin.Name -eq "Microsoft.BusinessServer.Licensing.PowerShell"} and press ENTERYou will see some CAL powershell commands. Use "Get-CalSummary" to view a summary of your installed CALS. Use "Get-CalAssignment" to view the current CAL assignments. IMPORTANT NOTE: When you add, change,or delete domain user accounts, remember to rerun step#6 so it can assign or free-up CALs accordingly IMPORTANT NOTE#2: There are 2 CALs reserved for the server's computername (per device CAL) and Administrator (per user CAL). These special CALs do not count against your normal CAL allocation. Do not attempt to manually re-assign CALs from these 2 accounts. Example if your server comes with 5 cals, you will actually see 7 CALS total when you do "get-calsummary" in powershell (since 2 are reserved) Name Category Object Type Edition NameOfYourSBSServer Built-in Device standard or premium Administrator Regular User standard or premium Well I hoped you had fun as I did. Next time I plan to stick to "Windows Server 20xx Standard" in the future. Had I known CALS were handled differently under "Windows SBS essential server" products, I would have thought twice. YMMV of course. I will continue to update this solution as needed.

In case anyone has this problem, this is because Windows Server Standard FE SP1/SP2 or "Windows Server 2008 for Windows Essential Server Solutions" needs you to configure WinWESS CAL licensing manually (Unlike Server 2008 standard which goes by the "honor system"): http://technet.microsoft.com/en-us/library/dd279492(v=ws.10).aspx PREFACE: Do these steps after normal business hours, because you must assign CALS after "step 2". Otherwise your domain users will get the Your account is configured to prevent you from using this computer. Please use another computer. error message when they logon. To enable the user to log on, you MUST assign a CAL to the user account (per user) or the computer (per device): (Get ready for some fun, I wasn't expecting to be a CLICommandGod(TM) to use "Windows Server 2008 for Windows Essential Server Solutions" Follow the 3 steps below, and this will allow WinWESS CAL licensing to work properly. Step 1: install Windows PowerShell (during the install it appears to hang, but actually takes awhile to install, give it time to finish) On the desktop, click Start, click Administrative Tools, and then click Server Manager.At the User Account Control prompt, click Continue.In the Server Manager dialog box, in the console pane, click Features.In the Features pane, click Add Features.In the Features list, select Windows PowerShell, and then click Next.On the Confirmation page, click Install.When the installation is finished, click Close. Step 2: Install client access licensing Insert the WinWESS DVD, and then, on the desktop, click Start, click All Programs, and then click Accessories. Right-click Command Prompt, and then click Run as administrator.At the command prompt, type msiexec /i G:\tools\licensing\WinSB.msi /qn and then press ENTER. (Assuming G is the DVD drive letter where you inserted the WinWESS DVD. Wait a few minutes for this step to complete)At the command prompt, type cd C:\Windows\system32 and then press ENTER. (C is the drive where you installed WinWESS.)At the command prompt, type LicensingSetupForWinSB.cmd and then press ENTER. (This step should go fairly quickly) Now verify by checking server event ID#31 logs: Go to server manager>diagnostics>Event Viewer>Applications and services logs>Microsoft>Windows>Server Infrastructure Licensing>OperationalLook for event ID#31, it should say "The external licensing enforcement check passed.". If it does, give yourself a high five, now it's not shutting itself off in "x" days/hours due to failed licensing compliance checks. Hooray! (OK Step 3 is REALLY important, you must now assign CALS "per device/computer" or "per user" before normal business hours or the domain users will get: Your account is configured to prevent you from using this computer. Please use another computer. Isn't that great? (After reading both URL's, realizing EBS Administration Console gui is completely crippled or missing on my server, and further frying my brain, I combined the steps and came up with the 8 step method) my original sources: http://blogs.technet.com/b/essentialbusinessserver/archive/2009/10/12/understanding-ebs-client-licensing.aspx; http://technet.microsoft.com/en-us/library/dd252607(v=ws.10).aspx Step 3: View CAL summary, Assign CALs via PowerScript, View CAL Assignments Click the start button>all programs>administrative tools, find and right click "run as administrator" the shortcut labeled "windows powershell modules" (you'll get a message saying powershell is disabled due to server policy, just ignore)In the same Windows PowerShell window, type Set-ExecutionPolicy RemoteSigned, and then press ENTER. (powershell commands are now enabled). Now download the file located here or you can go to this site and manually download it: https://skydrive.live.com/?cid=d5fe25afb6c3615f&id=D5FE25AFB6C3615F%21136 look for file "bulkassigncals.ps1"IMPORTANT! before running the CAL assignment powershell script, go to active directory and delete/disable any old domain user accounts, test domain user accounts, or accounts from people that left the company, so the script won't assign CALS to them.In the same Windows PowerShell window, CD into the directory where you downloaded the "bulkassigncals.ps1" fileIn the same Windows PowerShell window, type this command .\bulkassignCALs.ps1 standard and hit ENTER (yes that is a ".\" in front with no space). If you have the premium edition, replace the syntax word "standard" with "premium"). The script will now assign CALS to every domain user account [without a CAL] as "Per User CAL".In the same Windows PowerShell window, type this command gcm -type cmdlet | ? {$_.PSSnapin.Name -eq "Microsoft.BusinessServer.Licensing.PowerShell"} and press ENTERYou will see some CAL powershell commands. Use "Get-CalSummary" to view a summary of your installed CALS. Use "Get-CalAssignment" to view the current CAL assignments. IMPORTANT NOTE: When you add, change,or delete domain user accounts, remember to rerun step#6 so it can assign or free-up CALs accordingly Well I hoped you had fun as I did. Next time I plan to stick to "Windows Server 20xx Standard" in the future. Had I known CALS were handled differently under "Windows SBS essential server" products, I would have thought twice. YMMV of course. I will continue to update this solution as needed.

In case anyone still has this problem, this is because Windows Server Standard FE SP1 or "Windows Server 2008 for Windows Essential Server Solutions" apparently needs you to configure WinWESS CAL licensing (Unlike Server 2008 standard which goes by the "honor system"): http://technet.microsoft.com/en-us/library/dd279492(v=ws.10).aspx Follow the 2 steps below, and this will allow WinWESS licensing to work properly: Step 1: install Windows PowerShell (during the install it appears to hang but actually takes awhile to install, give it time to finish) On the desktop, click Start, click Administrative Tools, and then click Server Manager. At the User Account Control prompt, click Continue. In the Server Manager dialog box, in the console pane, click Features. In the Features pane, click Add Features. In the Features list, select Windows PowerShell, and then click Next. On the Confirmation page, click Install. When the installation is finished, click Close. Step 2: Install client access licensing Insert the WinWESS DVD, and then, on the desktop, click Start, click All Programs, and then click Accessories. Right-click Command Prompt, and then click Run as administrator. At the command prompt, type msiexec /i G:\tools\licensing\WinSB.msi /qn, and then press ENTER. G is the drive where you inserted the WinWESS DVD. At the command prompt, type cd C:\Windows\system32, and then press ENTER. C is the drive where you installed WinWESS. At the command prompt, type LicensingSetupForWinSB.cmd, and then press ENTER. After the 2 steps are completed, you can verify it worked by checking server event logs: Go to server manager>diagnostics>Event Viewer>Applications and services logs>Microsoft>Windows>Server Infrastructure Licensing>OperationalLook at event ID 31, it should now say "The external licensing enforcement check passed." Also see: Manage WinWESSS CAL licensing: http://technet.microsoft.com/en-us/library/dd252607(v=ws.10).aspx