# Clarion 10/11 program running on Windows Server Core **URL:** \ **Category:** questions\ **Tags:** server-os\ **Created:** [April 4, 2019, 7:55pm UTC](https://clarionhub.com/t/clarion-10-11-program-running-on-windows-server-core/2541 "2019-04-04T19:55:20Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![anon23294430](https://clarionhub.com/user_avatar/clarionhub.com/anon23294430/32/3829_2.png) [@anon23294430](https://clarionhub.com/u/anon23294430)\ **Post date:** [March 24, 2022, 5:24pm UTC](https://clarionhub.com/t/clarion-10-11-program-running-on-windows-server-core/2541/11 "2022-03-24T17:24:03Z")
OLE is definitely a desktop function and the MS info on server core differences [What is Server Core? | Microsoft Docs](https://docs.microsoft.com/en-us/windows-server/administration/server-core/what-is-server-core) and [DLLs Included with Server Core (Windows) | Microsoft Docs](https://docs.microsoft.com/en-us/previous-versions//ms723876(v=vs.85)?redirectedfrom=MSDN) suggests the desktop experience would be a security risk. Dependency Walker (Depends.exe) should hilight all the api dll’s a clarion app needs, but if you dont need that functionality on server core, isnt the compiler excluding the api calls? If you do need that functionality, could you do a work around like using check boxes (if that doesnt need the OLE dll) or command line switch or configuration txt file? Alot of headless linux apps just use a config file of sorts and I get the impression MS are trying to make server core a headless gui/desktop less experience, but I’ve not messed around with it to really be able to comment on the subject other than the info that can be read online. --- _[View the full topic](https://clarionhub.com/t/clarion-10-11-program-running-on-windows-server-core/2541)._