ScreenFlow 7 is powerful, easy-to-use screencasting software for the Mac. With ScreenFlow you can record the contents of your entire monitor while also capturing your video camera, microphone.
As I have roamed the internet for some kind of help on this and found nothing of relivence, I have come to you guys in here. I work on a workflow system called 'TRUEFLOW' in the print industry. I am trying to run the 'TRUEFLOW Client' in my mac. I am told it does work as it is a requirment in the industry. When I load the client and attempt to run it, I get the error 'Java Application Stub has unexpetedly quit' I called screen and told them of this, and they told my to download the 'java updates 1.4.2'. I did this but it still does not work. Before I go back to Screen again and again and again, I wonderd if someone very very clever in here could enlighten me any more, and is it something I can rectify? Crash Log below. An anticipated thank you to anyone who might be able to help.
Date/Time: 2005-10-04 08:25:36 +0100
OS Version: 10.3.9 (Build 7W98)
Report Version: 2
Command: JavaApplicationStub
Path: /Volumes/Trueflow 3 Client/Trueflow Client.app/Contents/MacOS/JavaApplicationStub
Version: ??? (3.03TF309T1A1)
PID: 559
Thread: 13
Exception: EXC BADACCESS (0x0001)
Codes: KERN PROTECTIONFAILURE (0x0002) at 0x00000048
Thread 0:
0 libSystem.B.dylib 0x90007878 mach msgtrap + 0x8
1 libSystem.B.dylib 0x900073f8 mach_msg + 0x38
2 com.apple.CoreFoundation 0x901c15e8 __CFRunLoopRun + 0x350
3 com.apple.CoreFoundation 0x901c5d74 CFRunLoopRunSpecific + 0x148
4 com.apple.HIToolbox 0x92886e10 RunCurrentEventLoopInMode + 0xac
5 com.apple.HIToolbox 0x9288d53c ReceiveNextEventCommon + 0x17c
6 com.apple.HIToolbox 0x928af638 BlockUntilNextEventMatchingListInMode + 0x60
7 com.apple.AppKit 0x92e822ac _DPSNextEvent + 0x180
8 com.apple.AppKit 0x92e98d2c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 0x74
9 com.apple.AppKit 0x92ead0ac -[NSApplication run] + 0x21c
10 libawt.jnilib 0x8108bc3c +[AWTStarter startAWT:] + 0xd0
11 com.apple.Foundation 0x90a4b0f8 __NSFireMainThreadPerform + 0x108
12 com.apple.CoreFoundation 0x90214558 __CFRunLoopPerformPerform + 0x88
13 com.apple.CoreFoundation 0x901c3b90 __CFRunLoopDoSources0 + 0x1fc
14 com.apple.CoreFoundation 0x901c1448 __CFRunLoopRun + 0x1b0
15 com.apple.CoreFoundation 0x901c5d74 CFRunLoopRunSpecific + 0x148
16 ...ple.JavaApplicationLauncher 0x81f338b4 Z11startupJavaiiPPKcPK14__CFDictionary14BuilderVersionS0_S1 + 0x128
17 ??? 0x00009574 0x1000 + 0x8574
18 ??? 0x000093e8 0x1000 + 0x83e8
Thread 1:
0 libSystem.B.dylib 0x90007878 mach msgtrap + 0x8
1 libSystem.B.dylib 0x900073f8 mach_msg + 0x38
2 libjvm.dylib 0x990083b8 JVM_GetClassAccessFlags + 0x1168
3 libjvm.dylib 0x990036a0 mh_dylibheader + 0x36a0
4 libjvm.dylib 0x99004488 JVM_Yield + 0x2f8
5 libjvm.dylib 0x9903e5b8 JVM_CurrentClassLoader + 0xc78
6 <<00000000>> 0x0473efbc 0 + 0x473efbc
7 <<00000000>> 0x0472ff90 0 + 0x472ff90
8 <<00000000>> 0x0472ff90 0 + 0x472ff90
9 <<00000000>> 0x0472ff90 0 + 0x472ff90
10 <<00000000>> 0x0472ff90 0 + 0x472ff90
11 <<00000000>> 0x0472ff90 0 + 0x472ff90
12 <<00000000>> 0x0472ff90 0 + 0x472ff90
13 <<00000000>> 0x0472d16c 0 + 0x472d16c
14 libjvm.dylib 0x9901afe8 JVM_GetCPMethodClassNameUTF + 0xb38
15 libjvm.dylib 0x9903c438 JVM_GetCPClassNameUTF + 0x998
16 libjvm.dylib 0x990b4224 JVM_IsNaN + 0x5b24
17 libjvm.dylib 0x990dbbb4 __floatdisf + 0xef4
18 libjvm.dylib 0x99109700 JVM_InvokeMethod + 0x1f0
19 <<00000000>> 0x047365c0 0 + 0x47365c0
20 <<00000000>> 0x0472fea0 0 + 0x472fea0
21 <<00000000>> 0x0472fea0 0 + 0x472fea0
2
Date/Time: 2005-10-04 08:25:36 +0100
OS Version: 10.3.9 (Build 7W98)
Report Version: 2
Command: JavaApplicationStub
Path: /Volumes/Trueflow 3 Client/Trueflow Client.app/Contents/MacOS/JavaApplicationStub
Version: ??? (3.03TF309T1A1)
PID: 559
Thread: 13
Exception: EXC BADACCESS (0x0001)
Codes: KERN PROTECTIONFAILURE (0x0002) at 0x00000048
Thread 0:
0 libSystem.B.dylib 0x90007878 mach msgtrap + 0x8
1 libSystem.B.dylib 0x900073f8 mach_msg + 0x38
2 com.apple.CoreFoundation 0x901c15e8 __CFRunLoopRun + 0x350
3 com.apple.CoreFoundation 0x901c5d74 CFRunLoopRunSpecific + 0x148
4 com.apple.HIToolbox 0x92886e10 RunCurrentEventLoopInMode + 0xac
5 com.apple.HIToolbox 0x9288d53c ReceiveNextEventCommon + 0x17c
6 com.apple.HIToolbox 0x928af638 BlockUntilNextEventMatchingListInMode + 0x60
7 com.apple.AppKit 0x92e822ac _DPSNextEvent + 0x180
8 com.apple.AppKit 0x92e98d2c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 0x74
9 com.apple.AppKit 0x92ead0ac -[NSApplication run] + 0x21c
10 libawt.jnilib 0x8108bc3c +[AWTStarter startAWT:] + 0xd0
11 com.apple.Foundation 0x90a4b0f8 __NSFireMainThreadPerform + 0x108
12 com.apple.CoreFoundation 0x90214558 __CFRunLoopPerformPerform + 0x88
13 com.apple.CoreFoundation 0x901c3b90 __CFRunLoopDoSources0 + 0x1fc
14 com.apple.CoreFoundation 0x901c1448 __CFRunLoopRun + 0x1b0
15 com.apple.CoreFoundation 0x901c5d74 CFRunLoopRunSpecific + 0x148
16 ...ple.JavaApplicationLauncher 0x81f338b4 Z11startupJavaiiPPKcPK14__CFDictionary14BuilderVersionS0_S1 + 0x128
17 ??? 0x00009574 0x1000 + 0x8574
18 ??? 0x000093e8 0x1000 + 0x83e8
Thread 1:
0 libSystem.B.dylib 0x90007878 mach msgtrap + 0x8
1 libSystem.B.dylib 0x900073f8 mach_msg + 0x38
2 libjvm.dylib 0x990083b8 JVM_GetClassAccessFlags + 0x1168
3 libjvm.dylib 0x990036a0 mh_dylibheader + 0x36a0
4 libjvm.dylib 0x99004488 JVM_Yield + 0x2f8
5 libjvm.dylib 0x9903e5b8 JVM_CurrentClassLoader + 0xc78
6 <<00000000>> 0x0473efbc 0 + 0x473efbc
7 <<00000000>> 0x0472ff90 0 + 0x472ff90
8 <<00000000>> 0x0472ff90 0 + 0x472ff90
9 <<00000000>> 0x0472ff90 0 + 0x472ff90
10 <<00000000>> 0x0472ff90 0 + 0x472ff90
11 <<00000000>> 0x0472ff90 0 + 0x472ff90
12 <<00000000>> 0x0472ff90 0 + 0x472ff90
13 <<00000000>> 0x0472d16c 0 + 0x472d16c
14 libjvm.dylib 0x9901afe8 JVM_GetCPMethodClassNameUTF + 0xb38
15 libjvm.dylib 0x9903c438 JVM_GetCPClassNameUTF + 0x998
16 libjvm.dylib 0x990b4224 JVM_IsNaN + 0x5b24
17 libjvm.dylib 0x990dbbb4 __floatdisf + 0xef4
18 libjvm.dylib 0x99109700 JVM_InvokeMethod + 0x1f0
19 <<00000000>> 0x047365c0 0 + 0x47365c0
20 <<00000000>> 0x0472fea0 0 + 0x472fea0
21 <<00000000>> 0x0472fea0 0 + 0x472fea0
2
Posted on
-->Applies to: Configuration Manager (current branch)
Configuration Manager supports installing client software on Windows and macOS computers.
General requirements and limitations
Review the following requirements and limitations for all clients:
- Changing the startup type or Log on as settings for any Configuration Manager service isn't supported. This change can prevent key services from running correctly.
Windows computers
To manage the following Windows OS versions, use the client that's included with Configuration Manager. For more information, see How to deploy clients to Windows computers.
Supported client OS versions
- Windows 10For more detailed information, see Support for Windows 10.
- Windows 8.1 (x86, x64): Professional, Enterprise
- Windows 7 with SP1 (x86, x64): Professional, Enterprise, and Ultimate
Windows Virtual Desktop
Windows Virtual Desktop is a preview feature of Microsoft Azure and Microsoft 365. Starting in version 1906, use Configuration Manager to manage these virtual devices running Windows in Azure.
Similar to a terminal server, some of these virtual devices allow multiple concurrent active user sessions. To help with client performance, Configuration Manager now disables user policies on any device that allows these multiple user sessions. Even if you enable user policies, the client disables them by default on these devices, which include Windows 10 Enterprise multi-session and terminal servers.
The client only disables user policy when it detects this type of device during a new installation. For an existing client of this type that you update to this version, the previous behavior persists. On an existing device, it configures the user policy setting even if it detects that the device allows multiple user sessions.
If you require user policy in this scenario, and accept any potential performance impact, use one of the following methods to enable user policy:
- In version 1910 and later, use client settings. In the Client Policy group, configure the following setting: Enable user policy for multiple user sessions.
- In version 1906, use the Configuration Manager SDK with the SMS_PolicyAgentConfig server WMI class. Set the new
PolicyEnableUserPolicyOnTS
property totrue
.
Note
You can't use co-management with a client running Windows 10 Enterprise multi-session.
Supported server OS versions
- Windows Server 2019: Standard, Datacenter Note 1
(Starting with Configuration Manager version 1806.) - Windows Server 2016: Standard, Datacenter Note 1
- Windows Storage Server 2016: Workgroup, Standard
- Windows Server 2012 R2 (x64): Standard, Datacenter Note 1
- Windows Storage Server 2012 R2 (x64)
- Windows Server 2012 (x64): Standard, Datacenter Note 1
- Windows Storage Server 2012 (x64)
- Windows Server 2008 R2 with SP1 (x64): Standard, Enterprise, Datacenter Note 1
- Windows Storage Server 2008 R2 (x86, x64): Workgroup, Standard, Enterprise
- Windows Server 2008 with SP2 (x86, x64): Standard, Enterprise, Datacenter Note 1
Server Core
The following versions specifically refer to the Server Core installation of the OS. Note 3
Windows Server semi-annual channel versions are Server Core installations, such as Windows Server, version 1809. As a Configuration Manager client, they're supported the same as the associated Windows 10 semi-annual channel version. For more information, see Support for Windows 10.
- Windows Server 2019 (x64) Note 2
- Windows Server 2016 (x64) Note 2
- Windows Server 2012 R2 (x64) Note 2
- Windows Server 2012 (x64) Note 2
- Windows Server 2008 R2 with no service pack, or with SP1 (x64)
- Windows Server 2008 SP2 (x86, x64)
Note 1
Configuration Manager tests and supports Windows Server Datacenter editions, but isn't officially certified for Windows Server. Configuration Manager hotfix support isn't offered for issues that are specific to Windows Server Datacenter Edition. For more information on the Windows Server certification program, see Windows Server Catalog.
Note 2
To support client push installation, add the File Server service of the File and Storage Services server role. For more information about installing Windows features on Server Core, see Install roles, role services, and features by using Windows PowerShell cmdlets.
Note 3
The new Software Center app isn't supported on any version of Windows Server Core.
Windows Embedded computers
Manage Windows Embedded devices by installing the Configuration Manager client on the device. For more information, see Planning for client deployment to Windows Embedded devices.
Requirements and limitations
- All client features are supported on Windows Embedded systems that don't have write filters enabled.
- Clients that use one of the following are supported for all features except power management:
- Enhanced Write Filters (EWF)
- RAM File-Based Write Filters (FBWF)
- Unified Write Filters (UWF)
- The application catalog isn't supported for any Windows Embedded device.
Supported OS versions
- Windows 10 Enterprise (x86, x64)
- Windows 10 IoT Enterprise (x86, x64)
This version includes the long-term servicing channel (LTSC). For more information, see Overview of Windows 10 IoT Enterprise. - Windows Embedded 8.1 Industry (x86, x64)
- Windows Embedded 8 Standard (x86, x64)
- Windows Thin PC (x86, x64)
- Windows Embedded POSReady 7 (x86, x64)
- Windows Embedded Standard 7 with SP1 (x86, x64)
Windows CE computers
Manage Windows CE devices with the Configuration Manager mobile device legacy client that is included with Configuration Manager.
Requirements and limitations
- The mobile device client requires 0.78 MB of storage space for installation. Sign-in can require up to 256 KB of additional storage space.
- Features for these mobile devices vary by platform and client type. For information about which management functions are supported, see Choose a device management solution.
Supported OS versions
- Windows CE 7.0 (ARM and x86 processors)NoteSupport is deprecated for Windows CE 7.0 in Configuration Manager. For more information, see Removed and deprecated items for Configuration Manager clients.
Supported languages include
- Chinese (simplified and traditional)
- English (US)
- French (France)
- German
- Italian
- Japanese
- Korean
- Portuguese (Brazil)
- Russian
- Spanish (Spain)
Extended Security Updates and Configuration Manager
The Extended Security Updates (ESU) program is a last resort option for customers who need to run certain legacy Microsoft products past the end of support. It includes Critical and/or Important security updates (as defined by the Microsoft Security Response Center (MSRC)) for a maximum of three years after the product’s End of Extended Support date.
Products that are beyond their support lifecycle aren't supported for use with Configuration Manager. This includes any products that are covered under the ESU program. Security updates released under the ESU program will be published to Windows Server Update Services (WSUS). These updates will appear in the Configuration Manager console. While products that are covered under the ESU program are no longer supported for use with Configuration Manager, the latest released version of Configuration Manager current branch can be used to deploy and install Windows security updates released under the program. The latest released version can also be used to deploy supported OSes via operating system deployment (OSD).
Client management features not related to Windows software update management or OSD will no longer be tested on the operating systems covered under the ESU program and we don't guarantee that they'll continue to function. It's highly recommended to upgrade or migrate to a current version of the operating systems as soon as possible to receive client management support.
Mac computers
Manage Apple Mac computers with the Configuration Manager client for macOS.
The macOS client installation package isn't supplied with the Configuration Manager media. Download the Clients for Additional Operating Systems from the Microsoft Download Center.
For more information, see How to deploy clients to Macs.
Requirements and limitations
- Installing or running the Configuration Manager client for macOS on computers under an account other than root isn't supported. Doing so can prevent key services from running correctly.
Supported versions
- macOS Mojave (10.14)
- macOS High Sierra (10.13)
- macOS Sierra (10.12)
- macOS 10.11 (El Capitan)
- macOS 10.10 (Yosemite)
- macOS 10.9 (Mavericks)
- macOS 10.8 (Mountain Lion)
- macOS 10.7 (Lion)
- macOS 10.6 (Snow Leopard)
Linux and UNIX servers
Important
Configuration Manager version 1902 drops support for Linux and UNIX as a client. Deprecation was announced with version 1802. Consider Microsoft Azure Management for managing Linux servers. Azure solutions have extensive Linux support that in most cases exceed Configuration Manager functionality, including end-to-end patch management for Linux.
The Linux and UNIX client installation packages aren't supplied with the Configuration Manager media. Download the Clients for Additional Operating Systems from the Microsoft Download Center. In addition to client installation packages, the client download includes the script that manages the installation of the client on each computer.
Requirements and limitations
- To review OS file dependencies for the client for Linux and UNIX, see Prerequisites for client deployment to Linux and UNIX servers.
- For an overview of supported management capabilities for Linux or UNIX, see How to deploy clients to UNIX and Linux servers.
- For supported versions of Linux and UNIX, the listed version includes all subsequent minor versions. For example, CentOS version 6 includes CentOS 6.3. Similarly, support for an OS that uses service packs (such as SUSE Linux Enterprise Server 11 SP1) includes subsequent service packs for that OS version.
- For information about client installation packages and the Universal Agent, see How to deploy clients to UNIX and Linux servers.
Supported versions
The following versions are supported by using the indicated .tar file.
AIX
Version | TAR file |
---|---|
Version 6.1 (Power) | ccm-Aix61ppc.<build>.tar |
Version 7.1 (Power) | ccm-Aix71ppc.<build>.tar |
CentOS
Version | TAR file |
---|---|
Version 5 x86 | ccm-Universalx86.<build>.tar |
Version 5 x64 | ccm-Universalx64.<build>.tar |
Version 6 x86 | ccm-Universalx86.<build>.tar |
Version 6 x64 | ccm-Universalx64.<build>.tar |
Version 7 x64 | ccm-Universalx64.<build>.tar |
Debian
Version | TAR file |
---|---|
Version 5 x86 | ccm-Universalx86.<build>.tar |
Version 5 x64 | ccm-Universalx64.<build>.tar |
Version 6 x86 | ccm-Universalx86.<build>.tar |
Version 6 x64 | ccm-Universalx64.<build>.tar |
Version 7 x86 | ccm-Universalx86.<build>.tar |
Version 7 x64 | ccm-Universalx64.<build>.tar |
Version 8 x86 | ccm-Universalx86.<build>.tar |
Version 8 x64 | ccm-Universalx64.<build>.tar |
HP-UX
Version | TAR file |
---|---|
Version 11iv3 IA64 | ccm-HpuxB.11.31i64.<build>.tar |
Oracle Linux
Version | TAR file |
---|---|
Version 5 x86 | ccm-Universalx86.<build>.tar |
Version 5 x64 | ccm-Universalx64.<build>.tar |
Version 6 x86 | ccm-Universalx86.<build>.tar |
Version 6 x64 | ccm-Universalx64.<build>.tar |
Version 7 x64 | ccm-Universalx64.<build>.tar |
Red Hat Enterprise Linux (RHEL)
Version | TAR file |
---|---|
Version 5 x86 | ccm-Universalx86.<build>.tar |
Version 5 x64 | ccm-Universalx64.<build>.tar |
Version 6 x86 | ccm-Universalx86.<build>.tar |
Version 6 x64 | ccm-Universalx64.<build>.tar |
Version 7 x64 | ccm-Universalx64.<build>.tar |
Solaris
Version | TAR file |
---|---|
Version 10 x86 | ccm-Sol10x86.<build>.tar |
Version 10 SPARC | ccm-Sol10sparc.<build>.tar |
Version 11 x86 | ccm-Sol11x86.<build>.tar |
Version 11 SPARC | ccm-Sol11sparc.<build>.tar |
SUSE Linux Enterprise Server (SLES)
Version | TAR file |
---|---|
Version 10 SP1 x86 | ccm-Universalx86.<build>.tar |
Version 10 SP1 x64 | ccm-Universalx64.<build>.tar |
Version 11 SP1 x86 | ccm-Universalx86.<build>.tar |
Version 11 SP1 x64 | ccm-Universalx64.<build>.tar |
Version 12 x64 | ccm-Universalx64.<build>.tar |
Ubuntu
Version | TAR file |
---|---|
Version 10.04 LTS x86 | ccm-Universalx86.<build>.tar |
Version 10.04 LTS x64 | ccm-Universalx64.<build>.tar |
Version 12.04 LTS x86 | ccm-Universalx86.<build>.tar |
Version 12.04 LTS x64 | ccm-Universalx64.<build>.tar |
Version 14.04 LTS x86 | ccm-Universalx86.<build>.tar |
Version 14.04 LTS x64 | ccm-Universalx64.<build>.tar |
Version 16.04 LTS x86 | ccm-Universalx86.<build>.tar |
Version 16.04 LTS x64 | ccm-Universalx64.<build>.tar |
On-premises MDM
Configuration Manager has built-in capabilities for managing mobile devices that are on-premises without installing client software. For more information, see Manage mobile devices with on-premises infrastructure.
Supported operating systems
- Windows 10 Pro (x86, x64)
- Windows 10 Pro Enterprise (x86, x64)
- Windows 10 IoT Enterprise (x86, x64)
This version includes the long-term servicing channel (LTSC). For more information, see Overview of Windows 10 IoT Enterprise. - Windows 10 IoT Mobile Enterprise
- Windows 10 Team for Surface Hub
- Windows 10 Mobile
- Windows 10 Mobile EnterpriseNoteSupport is deprecated for Windows 10 Mobile and Windows 10 Mobile Enterprise in Configuration Manager. For more information, see Removed and deprecated items for Configuration Manager clients.
Exchange Server connector
Configuration Manager supports limited management of devices that connect to your Exchange Server, without installing the Configuration Manager client. For more information, see Manage mobile devices with Configuration Manager and Exchange.
Supported versions of Exchange Server
- Exchange Online (Office 365): This version includes Business Productivity Online Standard Suite
- Exchange Server 2016
- Exchange Server 2013
- Exchange Server 2010 SP1 or Exchange Server 2010 SP2