Apple has just posted a pre-release build of OS X Server translation 4.0 on its developer portal site. The update is designed for systems running the approaching OS X 10.10 Yosemite and has a build number of 14S323. The seed notes are below :

OS X Server 4.0 Developer Preview OS X Server 4.0 Developer Preview 14S323 ( app interpretation 3.5.9 ) is now available for testing. This translation is designed for OS X Yosemite and includes many modern features and improvements. Minimum System Requirements To install OS X Server 4.0 Developer Preview 14S323, you need one of these computers : • iMac ( mid 2007 or newer ) • MacBook ( late 2008 Aluminum, or early on 2009 or newer ) • MacBook Pro ( Mid/Late 2007 or newer ) • MacBook Air ( belated 2008 or newer ) • Mac miniskirt ( early 2009 or newer ) • Mac Pro ( early on 2008 or newer ) • Xserve ( early on 2009 ) Your Mac needs : • OS X Yosemite Developer Preview • Atleast2GBofRAM • At least 10 GB of available harrow space ( 50 GB if you wish to use Caching Server ) Clean installs, updates from OS X Server 4.0 Developer Preview 14S310 and upgrade and migration from OS X Snow Leopard, OS X Lion, OS X Mountain Lion, and OS X Mavericks systems are supported ( exceptions noted below ) for this seed. What ’ second New In OS X Server 4.0 Developer Preview Server Application • OS X Server can perform network diagnostic tests to verify your waiter is accessible from the Internet. Network diagnostic tests verify reachability by checking your server ’ s host name, and serve ports. • Firewall and user/group-based service access controls can now be defined in the Access yellow journalism of Server paneling. Access restrictions may be applied in multiple levels – for all networks, local networks, this Mac, custom networks, and for specific users and groups. File Sharing • SMB 3 is the default protocol for sharing files in OS X Yosemite. SMB 3 helps protect against tampering and eavesdropping by encrypting and signing data “ in-flight. ” In addition to SMB 3, OS X Yosemite maintains confirm for SMB 2, AFP and SMB network file share protocols, automatically selecting the appropriate protocol as needed. • SMB 3 provides end-to-end encoding to protect data and fasten communication on untrusted networks. SMB 3 uses AES CCM for encoding to ensure communications between node and server are individual. • To guard against tamper, SMB 3 adds a touch to every packet transmitted over the wire. SMB 3 uses AES-CMAC to validate the integrity of the signature, ensuring the packets have not been intercepted, changed or replayed and that communication between hosts is authenticated and authorized. Profile Manager Profile Manager features new cargo settings and Mobile Device Management ( MDM ) support for new features in io 8 and OS X Yosemite. io and OS X • MDM support for device renaming • MDM question to display which VPP report is configured on a device, if any • Network settings for WPA-2 Enterprise and WPA2-PSD security types • VPN settings to support “ Always On ” and Internet Key Exchange ( IKEv2 ) iOS 8 • MDM support for pushing the initiation of media assets including PDF, EPUB and iBook Author files • MDM question to determine the most late iCloud backup • Restriction setting to Allow user to configure restrictions on a device • Restriction setting to restrict cellular data custom • Restriction context to allow or restrict consumption of Handoff • Restriction setting to prevent accompaniment of managed books • Restriction jell to prevent synchronize of highlights and notes of managed books • Restriction set to allow Internet results in Spotlight search • Restriction setting to Allow Erase of All Content and Settings • Restriction setting to Allow Managed Apps to Store Data in iCloud • Network setting for EAP-SIM random key challenges • Updated Content Filter setting for third-party circuit board filters • Updated Mail setting with per-message S/MIME sign encoding switch • Managed Domains setting to manage world wide web and mail score domains OS X Yosemite • MDM support for OS X enterprise app initiation • AD Certificate settings to support AllowAllAppsAccess and KeyIsExtractable • SCEP and AD Certificate settings to allow specifying certificate renewal telling prison term • Passcode mise en scene to prevent login after a assign number of wrong attempts Mail Server • Simpler interface for setting up electronic mail for multiple domains. Calendar Server • Administrators can store address data for all meet rooms in the Calendar Server. This allows Calendar clients to associate map location with a schedule-able localization, subscribe travel times, etc. Caching Server • IP address roll registration to support caching content in non-NAT ’ erectile dysfunction networks. What ’ sulfur New and Noteworthy to Test • Upgrade and migration from OS X Snow Leopard and higher systems • Xsan Bug Reporting When reporting a tease, enter the follow instruction in Terminal, then attach the output to the bug report. $ sudo /Applications/Server.app/Contents/ServerRoot/usr/sbin/ serverloggather Known Issues Server App • On first establish following a migration from a OS X Server 3.1.2, Open Directory users and groups may not appear. The workaround is to quit Server App and relaunch. Wiki serve. Xsan Configuration Instructions • Create a SAN • Start Xsan and create a fresh SAN. This machine will become an Xsan Controller. • Joining a Controller to an existing SAN • Start Xsan and select to Join a SAN. • Clients • Use the “ Save Configuration Profile ” command available on the Xsan acid of Server App to add a node to the SAN and copy the profile to the customer. Install the profile on clients by double-clicking the profile and following the facility procedure. Configure SAN Clients Using Profile Manager Clients can be configured using an Xsan Configuration Profile generated using Profile Manager. 1. Enroll one of the Xsan controllers into Device Management of Profile Manager. 2. Enroll each SAN node into Device Management of Profile Manager. 3. Use Profile Manager to push the Xsan configuration profile to the Clients. 4. Install the Profile on each SAN node. Upgrade and Migration 1. 2. 3. upgrade or Migrate your bequest Primary MDC beginning • Launch Server App and turn Xsan ON • Select to Restore a former SAN shape Upgrade or Migrate your bequest Backup MDC ’ south ( one at at clock time ) • Launch Server App and turn Xsan ON • Select to Restore a previous SAN shape Upgrade or Migrate Xsan Clients • Xsan will not be enabled at the end of the upgrade/migration • Copy the Xsan Configuration Profile from one of the MDC ’ s and install on the client OR Configure SAN Clients using Profile Manager ( see notes above )

generator : https://themedipia.com
Category : Website hosting

Leave a Reply

Your email address will not be published.