Whether you just bought your first Mac or you're a longtime Apple customer, here's a look at some of the best Mac Apps for 2021. Select any app from the list below for a full breakdown of what. Hence, the introduction of Apple's own developer tools alongside Mac OS X. Included in the package was an IDE—Project Builder—that was a tweaked version of the IDE that came with NeXT, the. How to Save iOS SHSH2 Blobs. Jerry Cook; Updated on 2020-12-14 to Downgrade iOS; People who have been working with iOS jailbreaking are not strange with SHSH blobs. SHSH blob is a term for a small piece of data that is part of Apple's digital signature protocol for iOS restores and updates, designed to control the iOS versions that users can install on their iOS devices (iPhones, iPads, iPod.
-->This article describes the important system requirements for your Microsoft Azure Data Box Gateway solution and for the clients connecting to Azure Data Box Gateway. We recommend that you review the information carefully before you deploy your Data Box Gateway, and then refer back to it as necessary during the deployment and subsequent operation.
The system requirements for the Data Box Gateway virtual device include:
- Software requirements for hosts - describes the supported platforms, browsers for the local configuration UI, SMB clients, and any additional requirements for the hosts that connect to the device.
- Networking requirements for the device - provides information about any networking requirements for the operation of the virtual device.
Specifications for the virtual device
The underlying host system for the Data Box Gateway is able to dedicate the following resources to provision your virtual device:
Specifications | Description |
---|---|
Virtual processors (cores) | Minimum 4 |
Memory | Minimum 8 GB. We strongly recommend at least 16 GB. |
Availability | Single node |
Disks | OS disk: 250 GB Data disk: 2 TB minimum, thin provisioned, and must be backed by SSDs |
Network interfaces | 1 or more virtual network interface |
Supported OS for clients connected to device
Here is a list of the supported operating systems for clients or hosts connected to your device. These operating system versions were tested in-house.
Operating system/platform | Versions |
---|---|
Windows Server | 2012 R2 2016 2019 |
Windows | 8, 10 |
SUSE Linux | Enterprise Server 12 (x86_64) |
Ubuntu | 16.04.3 LTS |
CentOS | 7.0 |
Mac OS | 10.14.1 |
Supported protocols for clients accessing device
Here are the supported protocols for clients accessing your device.
Protocol | Versions | Notes |
---|---|---|
SMB | 2.X, 3.X | SMB 1 isn't supported. |
NFS (currently in preview) | 3.0, 4.1 | Mac OS is not supported with NFS v4.1. |
Supported virtualization platforms for device
Operating system/platform | Versions | Notes |
---|---|---|
Hyper-V | 2012 R2 2016 2019 | |
VMware ESXi | 6.0 6.5 6.7 | VMware tools are not supported. |
Supported storage accounts
Here is a list of the supported storage accounts for your device.
Storage account | Notes |
---|---|
Classic | Standard |
General Purpose | Standard; both V1 and V2 are supported. Both hot and cool tiers are supported. |
Supported storage types
Here is a list of the supported storage types for the device.
File format | Notes |
---|---|
Azure block blob | |
Azure page blob | |
Azure Files |
Supported browsers for local web UI
Here is a list of the browsers supported for the local web UI for the virtual device.
Browser | Versions | Additional requirements/notes |
---|---|---|
Google Chrome | Latest version | |
Microsoft Edge | Latest version | |
Internet Explorer | Latest version | If Enhanced Security features are enabled, you may not be able to access local web UI pages. Disable enhanced security, and restart your browser. |
FireFox | Latest version |
Networking port requirements
The following table lists the ports that need to be opened in your firewall to allow for SMB, cloud, or management traffic. In this table, in or inbound refers to the direction from which incoming client requests access to your device. Out or outbound refers to the direction in which your Data Box Gateway device sends data externally, beyond the deployment: for example, outbound to the Internet.
Port no. | In or out | Port scope | Required | Notes |
---|---|---|---|---|
TCP 80 (HTTP) | Out | WAN | No | Outbound port is used for internet access to retrieve updates. The outbound web proxy is user configurable. |
TCP 443 (HTTPS) | Out | WAN | Yes | Outbound port is used for accessing data in the cloud. The outbound web proxy is user configurable. |
UDP 123 (NTP) | Out | WAN | In some cases See notes | This port is required only if you're using an internet-based NTP server. |
UDP 53 (DNS) | Out | WAN | In some cases See notes | This port is required only if you're using an internet-based DNS server. We recommend using a local DNS server. |
TCP 5985 (WinRM) | Out/In | LAN | In some cases See notes | This port is required to connect to the device via remote PowerShell over HTTP. |
TCP 5986 (WinRM) | Out/In | LAN | In some cases See notes | This port is required to connect to the device via remote PowerShell over HTTPS. |
UDP 67 (DHCP) | Out | LAN | In some cases See notes | This port is required only if you're using a local DHCP server. |
TCP 80 (HTTP) | Out/In | LAN | Yes | This port is the inbound port for local UI on the device for local management. Accessing the local UI over HTTP will automatically redirect to HTTPS. |
TCP 443 (HTTPS) | Out/In | LAN | Yes | This port is the inbound port for local UI on the device for local management. |
TCP 445 (SMB) | In | LAN | In some cases See notes | This port is required only if you are connecting via SMB. |
TCP 2049 (NFS) | In | LAN | In some cases See notes | This port is required only if you are connecting via NFS. |
URL patterns for firewall rules
Network administrators can often configure advanced firewall rules based on the URL patterns to filter the inbound and the outbound traffic. Your Data Box Gateway device and the Data Box Gateway service depend on other Microsoft applications such as Azure Service Bus, Azure Active Directory Access Control, storage accounts, and Microsoft Update servers. The URL patterns associated with these applications can be used to configure firewall rules. It is important to understand that the URL patterns associated with these applications can change. This in turn will require the network administrator to monitor and update firewall rules for your Data Box Gateway as and when needed.
We recommend that you set your firewall rules for outbound traffic, based on Data Box Gateway fixed IP addresses, liberally in most cases. However, you can use the information below to set advanced firewall rules that are needed to create secure environments.
Note
- The device (source) IPs should always be set to all the cloud-enabled network interfaces.
- The destination IPs should be set to Azure datacenter IP ranges.
URL pattern | Component or functionality |
---|---|
https://*.databoxedge.azure.com/* https://*.servicebus.windows.net/* https://login.windows.net | Azure Stack Edge / Data Box Gateway service Azure Service Bus Authentication Service |
http://*.backup.windowsazure.com | Device activation |
http://crl.microsoft.com/pki/* http://www.microsoft.com/pki/* | Certificate revocation |
https://*.core.windows.net/* https://*.data.microsoft.com http://*.msftncsi.com | Azure storage accounts and monitoring |
http://windowsupdate.microsoft.com http://*.windowsupdate.microsoft.com https://*.windowsupdate.microsoft.com http://*.update.microsoft.com https://*.update.microsoft.com http://*.windowsupdate.com http://download.microsoft.com http://*.download.windowsupdate.com http://wustat.windows.com http://ntservicepack.microsoft.com http://go.microsoft.com http://dl.delivery.mp.microsoft.com https://dl.delivery.mp.microsoft.com http://*.ws.microsoft.com https://*.ws.microsoft.com http://*.mp.microsoft.com | Microsoft Update servers |
http://*.deploy.akamaitechnologies.com | Akamai CDN |
https://*.partners.extranet.microsoft.com/* | Support package |
http://*.data.microsoft.com | Telemetry service in Windows, see the update for customer experience and diagnostic telemetry |
URL patterns for Azure Government
URL pattern | Component or functionality |
---|---|
https://*.databoxedge.azure.us/* https://*.servicebus.usgovcloudapi.net/* https://login.microsoftonline.us | Azure Stack Edge / Data Box Gateway service Azure Service Bus Authentication Service |
http://*.backup.windowsazure.us | Device activation |
http://crl.microsoft.com/pki/* http://www.microsoft.com/pki/* | Certificate revocation |
https://*.core.usgovcloudapi.net/* https://*.data.microsoft.com http://*.msftncsi.com | Azure storage accounts and monitoring |
http://windowsupdate.microsoft.com http://*.windowsupdate.microsoft.com https://*.windowsupdate.microsoft.com http://*.update.microsoft.com https://*.update.microsoft.com http://*.windowsupdate.com http://download.microsoft.com http://*.download.windowsupdate.com http://wustat.windows.com http://ntservicepack.microsoft.com http://*.ws.microsoft.com https://*.ws.microsoft.com http://*.mp.microsoft.com | Microsoft Update servers |
http://*.deploy.akamaitechnologies.com | Akamai CDN |
https://*.partners.extranet.microsoft.com/* | Support package |
http://*.data.microsoft.com | Telemetry service in Windows, see the update for customer experience and diagnostic telemetry |
Internet bandwidth
The devices are designed to continue to operate when your internet connection is slow or gets interrupted. In normal operating conditions, we recommend that you use:
- A minimum of 10-Mbps download bandwidth to ensure the device stays updated.
- A minimum of 20-Mbps dedicated upload and download bandwidth to transfer files.
Next step
Click here to return to the '10.3: Enable the floating Exposé blob' hint |
How bizarre!
There's some other mysterious preference keys, such as:
[code]wvous-tl-corner
wvous-tr-corner
wvous-bl-corner
wvous-br-corner[/code]
No idea what these are, but the Dock set wvous-br-corner equal to 5 by itself. I have no idea what it means.
There's also:
[code]wvous-showcorners
wvous-floater-style
wvous-maindisplay
wvous-olddesktop
wvous-spring-delay
wvous-spring[/code]
I've tried setting wvous-showcorners, wvous-floater-style, wvous-spring-delay, and wvous-spring with no obvious effects. Can anybody else figure out what these are?
D'OH!
Note to self: READ the preview before submitting!
top left corner
bottom left corner
top right corner
bottom right corner
Looks like those keys store hot corner settings.
I figured that's what the abbreviations meant, but hot corners for what? Also, the key that the Dock stored by itself was the bottom-right cornet set to 5? What does that mean?
I Ran the command in Terminal and also from terminal 'killall Dock' Since then I logged out last night and in the morning I saw something strange!!!
There was a finder window open floating under the Login List window. I noticed that the Home Folder was labeled Root, and I Could run apps as Root! When I logged in as a user I never recieved the desktop, and Still Had my Finder window. When I ran an app, it Ran as that User. When going to Logout (from the Apple) I would see either log out 'System Administrator' or log out '(the user's name)' depending on the Application I was currently Running. After Logging out then Back in as another User, I recieved it's desktop items, and Everything looks back to normal.
I grabbed a screen shot, but do not know how to post it.
Very Interesting!!!!!
Go to
http://www.imageshack.com/
and upload it there. Post the URL it gives you here.
...Wow. I just looked at the pictures again and realized that you did something with iTunes I never knew was possible!
Apparently trying to shrink the minimized version will get rid of the status fields entirely!
Maybe there should be a hint about that...
haha! You and I both got two-for-one hint!
You should get a copy of Kelby's Jaguar Killer Tips, or just look through it in the bookstore. The teeny iTunes window tip is there. In 'mini window mode', just grab the resize handle (lower right corner) and resize.
Ahhh! That screenshot! It's Rover from 'The Prisoner'! Run away!
(I can't find a decent picture of Rover to link to, but this page does a decent job of explaining the reference and conveying the imagery almost as well as the original :-)
---
--
DO NOT LEAVE IT IS NOT REAL
Oh wow, you're right!
Ok, I did some playing around an this is what I found.This will make little gray semi-circles appear in the corners
These refer to the exposé corners: tl=Top Left, tr=Top Right, bl=Bottom Left, br=Bottom Right Replace 'tl' with what corner you want, and 'x' with a number between 1 and 6. The number is the action that is performed by exposé 1=Nothing, the semicircle will disappear 2=All Windows 3=Application windows 4=Desktop 5=Start Screen Saver 6=Disable Screen Saver All these can be set from the Exposé preference pane.
This will change the Desktop effect. Instead of moving all the windows to the edges of the screen, it puts them all in a small box that can be dragged around the screen. Anyone had any luck with the others?
---
Do it today because tomorrow it may be illegal.
Cool Blob Future Mac Os Update
When I set wvous-olddesktop to 'no' to get the hyperzoomy effect, as soon as I zoomed to desktop then back, all metal windows stopped responding to mouse clicks - including Finder! So apparenly that effect was disabled because of some really weird interaction with the window server or something.
It's a shame, too, because that effect is much cooler than the windows all flying to the edge of the screen, and it could probably be argued that it's better for usability too (since it preserves spatial memory and so on).
Also, when I enabled the semicircles, the entire UI froze up as soon as I tried any Expose action (though iTunes kept on playing).
It might make a difference that I'm just running on a G4/450 with a Rage 128. (I'm getting a Radeon soon, honest!)
Wow, I love the olddesktop effect!
BTW, metal windows work perfectly fine for me after using it.
Erm, nevermind. The Preview button just stopped working until I scrolled the scrollbar manually (scroll wheel didn't work). But it's working now after trying the exposé effect again. Weird.
Actually, I know the problem now. It leaves an invisible window (I assume) in the area where the windows shrink to that sucks up all clicks in that area. So wherever you place the tiny window, you can't click. Turning olddesktop back on fixes it, though.
I figured out wvous-spring and wvous-spring-delay.
By default, if you drag a file (or probably any drag, but only tested with files from the Desktop) to an Exposé'd window (i.e. start drag, start Exposé, drag to window) and hover over a window for 1 second, it will flash and select itself. Just like spring-loaded folders (Space works for selecting the window as well).
If you do defaults write com.apple.Dock wvous-spring -bool false and restart the Dock, this behaviour disappears. To restore, do -bool true instead (or do a defaults delete com.apple.Dock wvous-spring).
To change the delay before the spring, set wvous-spring-delay. The value is an integer in milliseconds (i.e. 1000 1 second). For example, to set it to 2 seconds, type defaults write com.apple.Dock wvous-spring-delay -int 2000.
This was driving me crazy for i had to shift the windows to get the mouse click working, and i was seeking some weeks to find the reason why...
So i got back to the old fashined way again.
Sure, it's the easy way - but fact is, The Blob, from crabby apple software, allows a set and forget blob. . . .of your own design! I'm always on a Powerbook, thus forever obsessing over screen real estate - but maybe you don't like overly-large glossy blue circles either.
Drop any graphic on The Blob's window. Now I have about a half-inch unobstrusive, pale blue green square in the corner below A-Dock's trash. That's plenty large as mouse/trackpad target.
Yeah, you have to enable the blob in Cocktail, Onyx, shell, whatever. Try the 'desktop square' option. . very cool.
Okay, I'm a little lost, so please bear with me. I used OnyX to turn on the blob and now the windows don't go to the sides when I hit F10.
If I go to Terminal and type
'defaults write com.apple.dock wvous-olddesktop -bool true'
minus the quotes, will that fix it?
D'oh!
F11. The one that's supposed to show the desktop.
I tried this in Panther and not only could I not get it to work, I lost my second monitor.
So far I have not been able to get it (the monitor) to come back. If I reboot into 10.8 which I have on another drive the monitor is still off but if I re-power it if comes back and works fine, until I start up in Panther again when it disappears.
I have a G4 mirrored drive door that is original except for two extra internal drives.
10.8? What are you, part of some super-secret developer program from the future? :D
When you said 10.8, did you mean 10.2.8? Expose is only a feature in 10.3 and higher.
If you added information to your com.apple.dock and you are using Jaguar, I'm guessing that you are going to have to remove it somehow. And I'm afraid I don't know how to go about doing that.
Does this affect all users, or just your current user?
I hope this helps, if only a little.
robg... Looks like you've got a secret (software engineer) admirer:
http://www.versiontracker.com/dyn/moreinfo/macosx/21323
-Jesse
Does changing the images change its size, or is there another way?
I would find this feature really nicely useful if I could make the blob a little smaller and toss it in a rather specific place on my screen (currently unoccupied) but it is too big right now.
Put the blob mostly offscreen in a corner and then you have a little blue semi-circle that when clicked triggers expose as noted in the hint. I put it off the bottom-left corner. Just a simple way to make the blob smaller. I like it. Of course you can set the corners to trigger expose just by moving to the corner, but I find that with such settings I frequently accidentally trigger expose. Gets annoying. The blob off the corner works much better for me. I wish I could set the default action to be show all windows instead of current apps windows. Any way to do that?
---
--- What?
I thought this would be pretty slick, but alas, when I enabled the Blob, and then tried to move it, I couldn't get the mouse pointer to drop the blob anywhere. The Blob stayed glued to the pointer. The keyboard could still talk to the computer, but the mouse was worthless (except as a Blob Bellboy).
Now, here's the setup for what it's worth: an AGP 400 with a kensington pocket mouse.
I'll just stick to slamming the mouse into the lower left corner...
I pulled the images out and shrunk them by 50% - works much better for me. Like others mentioned, the original was just too big.
I have panther, and I have enabled the blob, however I can't get rid of it. I've tried restarting after setting the bool value as me, and as root, and killall Dock. Nothin. If anyone has any advice let me know.
Ok, I fixed my problem by going to System/Library/CoreServices and then opening the dock package, then deleting the floater images. I archived them incase I want it back...but if anyone else had this problem that is a way to fix it.
I wish I had never seen this page. Right after typing that blue blob line into Terminal, my Kensington MouseWorks stopped working. I typed the 'false' line to get rid of the blob, but MouseWorks still isn't working. I uninstalled, reinstalled both the latest beta and the older final, to no avail. I think it did something to the dock, because as the system boots up, the MouseWorks drivers ARE working (the mouse moves very smoothly), and only cuts back to normal mouse movement when the Dock comes back up.
So my question is: what can you do to restore the Dock to the way it was before I typed anything into Terminal?
TransparentDock from
http://www.freerangemac.com
has a prefs selection to turn this puppy on and off
How come the Desktop effect on desktop is being ghost to the montior? When I click or drag anything on my desktop in same location as Desktop effect is at and it acted like the screen is locked into exact same form as Desktop effect...
---
www.artistz.tk
Cool Blob Future Mac Os Catalina
This is all great. I love the blob - my favorite way to activate Exposé. However, one question: how do I make the default action when I click on it the arrange-all-open-windows rather than the application windows of the current app? I would rather have all windows be the default and use the Option-Click combo for the other. (Too bad right-clicking with a two-button mouse doesn't do this!)
---
iMac 17, OS 10.3
This works well if you setup an AppleScript or Platypus app to turn it on and off. More info on Platypus here http://sveinbjorn.vefsyn.is/platypus .
to make a Platypus app I used TextEdit to make two one-line scripts. One to turn the blob on, and one to turn it off. Put the following line in TextEdit:
defaults write com.apple.dock wvous-floater -bool true; killall Dock
(change true to false for the script to turn it off.) From TextEdit's Format menu choose Make Plain Text. Save the script, then drag-and-drop it into Platypus and click 'Create'. Do the same for the script to turn it off, then put your Platypus apps in your Utilities folder, or where ever you may want to keep them.
Likewise, in AppleScript, this script will run the command in a terminal (if you don't want to mess with Platypus):
tell application 'Terminal'
activate
do script with command 'defaults write com.apple.dock wvous-floater -bool true; killall Dock'
end tell
It still works beautifully with Tiger
Running 10.4.10 on a new iMac; I got the blob to appear ONCE, when I tried to click and drag to another part of the desktop, it zipped way off to the upper left of the screen, so that only a slice of it was still showing; when I clicked on that, it disappeared entirely, never to return (despite multiple attempts using defaults write com.apple.dock wvous-floater -bool true and false) -- any suggestions??? I would love to have it back...