To install Mac OS X Lion on a virtual machine, we're going to use Virtualbox, which is a free and open-source virtualization suite. It's important to note that Windows virtualization programs do not 'officially' support Mac OS X, so you will not be able to enable full graphics support. This tutorial should only be taken as a proof of concept. There are three phases to making your application feel more like a native Mac OS X application when running on a Mac without changing the look and feel on other platforms. In this article we'll look at some of the runtime properties you can set to move the position of the main menu bar, customize the Application menu, and tweak the appearance.
We're Getting There Mac Os Download
-->When users report that they aren't getting email, it can be hard to find what's wrong. You might run through several troubleshooting scenarios in your mind. Is something wrong with Outlook? Is the Office 365 service down? Is there a problem with mail flow or spam filter settings? Or is the problem due to something that's outside your control, like the sender is on a global block list? Fortunately, Office 365 provides powerful automated tools that can help you find and fix a variety of problems.
First things first, check if there's a problem with Outlook or another email app
If only one user is reporting having trouble receiving email, there might be a problem with their email account or their email app. Have the affected user try the following solutions before you move on to admin-specific tasks.
Use Outlook on the web to look for missing messages - 5 minutes
If a user is receiving email in their Outlook on the web mailbox but not on the email app that's installed on their machine, that could indicate that there's an issue with the users machine or email app. Ask the user with the issue to sign in to Outlook on the web to verify that their Office 365 email account is working correctly.
Instructions:Sign in to Outlook on the web for business
Run Microsoft Support and Recovery Assistant to fix Outlook problems or account issues - 10 minutes
If a single user in your organization is having trouble receiving email, it could be due to a licensing issue, a profile problem, the wrong version of Outlook, or a mix of other issues. Fortunately, Support and Recovery Assistant finds and helps you fix most issues with Outlook or Office 365. As a first step in troubleshooting email delivery problems for Office 365 for business, we recommend that you download and run Microsoft Support and Recovery Assistant on the affected machine. Note that if you are experiencing issues with Outlook for Mac or are having mobile access issues, you can use the app to check your account settings, but you need to install it on a PC. After you sign in with the affected account, the app will check for issues. Users can typically download and run Support and Recovery Assistant without help from their Office 365 admin.
Let us fix your issueDownload and run Microsoft Support and Recovery Assistant
If the Support and Recovery Assistant app doesn't fix the email delivery issue, try these admin tools
As an Office 365 for business admin, you have access to several tools that can help you investigate why users can't get email. The following video gives a brief overview of the tools available to you.
The following tools are listed from the quickest to the most in-depth option.
Check Office 365 service health for Exchange Online issues - 5 minutes
The service health page lists the status of Office 365 services and indicates if there have been any recent service incidents. Use the following steps to check the service health. Dragon 3d mac os.
Where to sign in to Office 365 for business with your work or school account.
Select the app launcher icon in the upper-left and choose Admin.
Tip
Admin appears only to Office 365 administrators.
Can't find the app you're looking for? From the app launcher, select All apps to see an alphabetical list of the Office 365 apps available to you. From there, you can search for a specific app.
Under Service health, go to View the service health.
If there is an indication that ExchangeOnline service is degraded, email delivery might be delayed for your organization, and CompanyName service engineers are already working to restore service. Check the service health page for progress updates. In this case, you don't need to open a service request because CompanyName is already working to resolve the issue.
Use message trace for in-depth email delivery troubleshooting - 15 minutes
Sometimes an email message gets lost in transit, or it can take a lot longer than expected for delivery, and your users can wonder what happened. The message trace feature lets you follow messages as they pass through your Exchange Online service. Getting detailed information about a specific message lets you efficiently answer your user's questions, troubleshoot mail flow issues, validate policy changes, and can prevent you from needing to contact technical support for assistance.
Open the message trace tool
If you're an Office 365 Midsize Business, Office 365 Business, or Office 365 Enterprise admin, you access and run the message trace tool through the Exchange admin center. To get there, do the following:
Where to sign in to Office 365 for business with your work or school account.
Select the app launcher icon in the upper-left and choose Admin.
Tip
Admin appears only to Office 365 administrators.
Can't find the app you're looking for? From the app launcher, select All apps to see an alphabetical list of the Office 365 apps available to you. From there, you can search for a specific app.
Go to Exchange.
Under mail flow, go to message trace.
If you're an Office 365 Small Business admin, do the following to find message trace:
Go to Admin > Service settings > Email, calendar, and contacts.
Under Email troubleshooting, click Troubleshoot message delivery.
Run a message trace and view delivery details of messages sent in the last week
By default, message trace is set to search for all messages sent or received by your organization in the past 48 hours. You can choose Search at the bottom of the page to generate this report. This report can give you a general idea about what is happening with mail flow in your organization. However, to troubleshoot a specific user's mail delivery issue, you want to scope the message trace results to that user's mailbox and the time frame that they expected to receive the message.
From the Date range menu, choose the date range that is closest to the time that the missing message was sent.
Use Add sender and Add recipient to add one or more senders and recipients, respectively.
Click Search to run the message trace.
The message trace results page shows all the messages that match the criteria that you selected. Typical messages are marked Delivered under the status column.
To see details about a message, choose the message and select ( Details).
Details appear with an explanation of what happened to the message. To fix the problem, follow the instructions in the How to fix it section.
We're Getting There Mac Os X
To search for a different message, you can click the Clear button on the message trace page, and then specify new search criteria.
View the results of a message trace that is greater than 7 days old
Message traces for items more than 7 days old are only available as a downloadable .CSV file. Because data about older messages is stored in a different database, message traces for older messages can take up to an hour. To download the .CSV file, do one of the following.
Click the link inside the email notification that is sent when the trace is completed.
To view a list of traces that were run for items that are more than 7 days old, click View pending or completed traces in the message trace tool.
In the resulting UI, the list of traces is sorted based on the date and time that they were submitted, with the most recent submissions appearing first.
When you select a specific message trace, additional information appears in the right pane. Depending on what search criteria you specified, this may include details such as the date range for which the trace was run, and the sender and intended recipients of the message.
Note
Message traces containing data that is greater than 7 days old are automatically deleted. They cannot be manually deleted.
Common questions about message trace
After a message is sent, how long before a message trace can pick it up?
Message trace data can appear as soon as 10 minutes after a message is sent, or it can take up to one hour.
Why am I getting a timeout error when I run a message trace?
The search is probably taking too long. Try simplifying your search criteria.
Why is my message taking so long to arrive to its destination?
Possible causes include the following:
The intended destination isn't responsive. This is the most likely scenario.
A large message takes a long time to process.
Latency in the service is causing delays.
The message was blocked by the filtering service.
QEMU is an open-source emulator for virtualizing computers. Unlike VMWare, it's able to both virtualize CPUs and emulate various CPU instruction sets. It's pretty powerful, free, and has a macOS port. There are alternate versions and different ways to install it. Still, in this example, I'm using Homebrew, a package manager for macOS/OSX that allows you to install software via the CLI and manage easily.
Now, this post wouldn't be very exciting if I tried this on my Mac Pro, but I decided to try it on my MacBook M1. Thus far, the community has succeeded in getting QEMU to install the ARM version Windows, so I decided to do the more silly path and get PPC and X86 working on Apple Silicon. I encountered very little resistance, which surprised me as I haven't seen/read anyone trying this route. It's surprsingly very usable but the usefulness is going to be limited. I was able to play Sim City 2000 on Mac OS 9.2 at a fairly high resolution. For the sake of brevity, I'm going to skip over installing Homebrew on an Apple M1, but you'll want to use the arch -x86_64 method, which requires prepending. I've gotten OS 10.0 and nearly gotten Windows 10 working on my M1.
Included below is the instruction for both Apple Silicon and Intel Macs.
Requirements
- Basic understanding of the terminal in OS X/macOS
- Apple Silicon (M1) computer (or Intel) Mac
- Xcode
- xcode-select (CLI Tools)
xcode-select --install
- Homebrew
Step 1: Install QEMU
This is the only step where Apple Silicon and Intel Macs differ. You'll need to install the x86 version of QEMU for the Apple silicon macs first.
Apple Silicon
x86 Intel Macs
Step 2: Create a disk image
The rest of the steps do not need any specification for M1 vs. Intel.
You can specify a route, but I just used the default pathing, the 2G = 2 GB below. You can get away with much less for OS X OS 9. If you'd like more space, change the size of the simulated HDD. .
Step 3: Launching the emulated computer and the tricky part: Formatting the HDD
Now that we have a blank hard disk image, we're ready to go.
Let's break this down so it's not just magic. The first command is the qemu core emulator, you can use things like 64-bit x86 CPU qemu-system-x86_64
or a 32-bit CPU qemu-system-i386
, but we're using a PPC, so we are using qemu-system-ppc
.
Next, we're declaring PC bios with -L pc-bios
, I'm unsure if this is necessary. This seems to be the default even in Mac QEMU. After that, the -boot
flag declares the boot drive. For those who remember the days of yore, C is the default drive for PCs, D is the default for the CD-Rom like a PC. It's weird, I know. -M
is the model flag. It's pretty esoteric, but QEMU uses OpenBIOS, and mac99 is the model for Beige G3s. The lowercase -m
is memory, expressed in megabytes, but you can use 1G or 2G for 1 or 2 gigabytes like the format utility. -hda
is the image we're using. Finally, -cdrom
is the installer image
Step 3.5: Special considerations between operating systems
I discovered that OS X 10.0's installer has a significant flaw: It doesn't have a disk utility. The disk images are black disks thus have no file system. If you want to run OS X 10.0, you'll need to first launch an installer that can format HFS like OS 9 or later versions of OS X, run the disk utility, format the image and then exit out of the emulator. The process would look like this:
Then format the drive from the utility, quit the emulator (control-c on the terminal window).
Tiger and Leopard requires USB emulation so you'll need to add -device
flags for a usb keyboard and a usb mouse, also both like a few extra -prom-env flags.
Power PC Leopard I can get to boot but it crashed twice during installs, this could be
Step 4: after the installer fininshes
You will end up seeing a failed boot screen after the installer finishes. This is normal. Instar mac os. Either quit the QEMU instance or use control-c in the terminal to close it. Now that it's installed, we want to boot off the internal drive.
MacOS 9 seems to do slightly better when adding the via=pmu and specifying the graphics.
Step 5: mounting disk images
There's not a lot to do with an OS without software. You can mount plenty of disk image formats
Bonus round: Trying for x86 64 Windows 10
Step 6: Multi CD-Rom Installs or swapping Disk Images
Older applications and OS installers require mutliple disk images. This can be done from via the CLI inside QEMU.
On the QEMU window press:
- Control-Alt-2 to bring up the console
change ide1-cd0 /path/to/image
- Control-Alt-1 to bring back the GUI
Thus far my Windows 10 experiment has been a lot less successful, I've gotten through the installer (it's unbearably slow) but it seems to hand on booting. It looks very feasible. I might have better luck using the 32 bit verison of windows.