Apple said all iMacs will now ship with Fusion Drives, right? Wasn't there an issue with using FileVault on Fusion Drives? Could I be misremembering something?

@AVmcclint Actually it's all iMacs priced higher than $1499 that now come with Fusion drives. And it's Thunderbolt imaging that's problematic with Fusion drives (AFAIK there's no issues with FV2). Of course AFS is going to change the world of imaging as we now know it, so the problems with Fusion imaging may become moot.

Hey!

Has anyone noticed a problem creating users in High Sierra?

I have an QuickAdd package running and it gets stuck at the "Creating user jssmanagement…" step, according to jamf.log

Also, some other IT users that I create using a package are visible in System Preferences but I can't see the corresponding Home folders. Could it be that HS is "smart enough" to delay the Home Folder creation until the user actually logs in?

Thanks.

I was quite enjoying the experience, Then, My Jamf policy for "more than 3 updates available" killed it!

Black screen... oh dear..

I'm investigating what 'broke' and will post my findings...

Awesome wallpaper though... Looks just like a picture of a drive between Dundee and Perth (Scotland) during Autumn.

Beautiful spalsh of colour!

APFS now supported in VM Fusion 8

Lock Screen was already in macOS, the key command is Command-Opt-Eject/Power key. Looks like all they did was change the keybinding and make it a menu item. Still a nice improvement though, most Mac users don't appear to know about the current Lock Screen key combo.

In my experience the key command is that the Command-Opt-Eject/Power key triggered the setting in require password in after sleep or screen saver begins in the security system pref. However the screen lock menu item from Keychain prefs locks it right away independent of what that setting is.

C

The lock menu in the keychain prefs has been removed, also the "Command-Opt-Eject/Power key" or keychain menu lock screen methods both try to sleep the computer first, while the new Lock Screen under the Apple Menu takes you to the lock screen first. Command-Opt-Eject/Power key method still works.

Has anyone came across issues binding a High Sierra machine to an Active Directory.

I've tried this several times (manually, with a script and with a policy) and every time, after seemingly being properly bound, the machine won't come back from a reboot and it gets stuck on the Apple logo screen with about 70% of the bar full. After this, the only option is to erase the disk and reinstall macOS.

So now, I guess I should stop testing this until a new beta version comes out.

@bearzooka With Build 17A291m, our custom Active Directory binding scripts are working as expected.

@bearzooka Correction: I believe I've duplicated your issue post-reboot. Do you have a Radar number?

I am seeing the same issue with AD Bind version 17A291m were the OS runs as expected, then run the AD bind and the OS hangs at reboot.
The only fix is to re-install.

We are having the same bind issue using the JAMF policy that we currently use for 10.10-10.12 machines. Interestingly, I was able to manually bind using the Directory Utility. Once I restarted and tried to login it accepted my domain credentials, displayed how many days until my password expired and then told me I couldn't login because an error occurred.

@dan.snelson Please don't mind my n00b-ness but… what is a Radar number?
Thanks!

@bearzooka In case you'd already filed a bug report with Apple, I'd reference your case number with mine. (However, we're moving away from AD binding.)

Hi,
Are people still seeing the AD bind issue with the latest release (out yesterday, 17A306f)? Gonna try here in a bit, but just curious if it changed anything for anyone.

Thanks,
Matt

Beta 3 release notes:

"Known Issues in macOS High Sierra 10.13 beta

The following are known to exist in this release.
Active Directory

• Clients bound to an Active Directory domain may currently hang at boot."

@here I have a question in reference to the the release name of the high sierra when it is released. I am trying to get ahead of the game and apply the restricted software block through JAMF while we test to make sure everything work in our environment. Our employees are day one adopters and i want to avoid problems.

if someone is going to update to High Sierra, don't forget to prepare your Mac before - https://nektony.com/blog/how-to-prepare-your-mac-for-macos-high-sierra-update

It might be interesting to use native virtualization for macOS to create Hi Sierra lab environments for testing all sorts of things - imaging etc.

https://veertu.com/beta-high-sierra-environment-in-an-isolated-vm/

Has anyone experienced issues with system extension blocking (http://blog.eriknicolasgomez.com/2017/07/25/Kextpocalypse-High-Sierra-and-kexts-in-the-Enterprise/) breaking VMWare, AV or other enterprise products? We did a test and VMWare and our AV does not work without IT telling the user to specifically allow the software to load kernel extensions in System Settings. That might be okay for VMWare, but we'd rather not give users the option to run AV. We're looking for a solution to deploy our enterprise software at scale without physically touching each individual endpoint to add the team ID with the spctl kext-consent command in recovery mode. Anyone else worried about this?

@dmeehan Lots of folks are worried about this. Apple has been trying to point developers away from using Kernel Extensions for some time, though.

Their note on Enterprise App Distribution is hilarious, as if that process is feasible in any enterprise environment.

There's not a magical workaround for this that I'm aware of.

Best to get with your vendors and query about their plans for a compatible agent for this release that invalidates the need to perform those steps. See this post.

I am seeing issue with blocking the password hint at the FV login window and the loginwindow text too.

Anybody else? I have opened tickets in the seed program.

C

When I downloaded the 10.13. B1 version it did not update the FS to APFS, so not much different than before, other than a few nice features like the lock screen. How did you all get the APFS to perform the update to use the full extent of this new FS?

Hoping JAMF will be doing some nifty scripts and the such to allow us to lock a computer without losing the ability to see it and its associated IP for tracking purposes.

Apple limited the developer and public betas to only offer to upgrade to APFS on solid state drives, the 10.13 beta installs would give the choice when installing.