D-Tools will run on a Mac using Parallels and Boot Camp. We do not recommend that you attempt to use SI5.5 in Fusion VMware as clients have reported issues that we are unable to assist with. Although SI5.5 will work in Parallels and Boot Camp, we currently do not support any of the above integrations due to the following reasons. Apple has introduced a selection of interesting improvements for iOS and Mac admins in the recently introduced iOS 14, including new APIs for mobile device management (MDM) and usability improvements. Be sure to also check out InfoWorld's IT guide to managing Macs in the OS X Lion era, as well as our overview of 22 essential Mac tools for IT admins. Mac support tool No. 1: JAMF Casper Suite.
Mac Support and Networking Tips
D-Tools will run on a Mac using Parallels and Boot Camp. We do not recommend that you attempt to use SI5.5 in Fusion VMware as clients have reported issues that we are unable to assist with. Although SI5.5 will work in Parallels and Boot Camp, we currently do not support any of the above integrations due to the following reasons:
- Networking problems – OS X acts as the domain controller and assigns Windows XP or Vista its own IP, so the actual windows network cannot see it or vice-versa. You will have to modify Parallels, and Boot Camp Network Adapter settings to allow a bridged NIC connection in order for it to work.
- Standalone mode seems to work okay, but if you do not properly shut down the windows OS. All of your projects, data, and file updates will be deleted and they will revert back to the last time you properly shut down Windows. This happens in Parallels, and also in Boot Camp.
- Boot Camp seems to work the best, but requires Mac users to reboot into Boot Camp and out of OSX. It is the least favorite among most Mac users.
- SI5 was never developed to be used in a Virtual Mac environment using Parallels or Boot Camp. We cannot support SI5 running on anything other than a native Windows environment PC (32bit systems only).
- Even if you are using Boot Camp, you may still encounter issues with errors like “SQL does not accept remote connections” or “LANSync server is not online.” This is why we cannot offer any assistance or support for Mac users at this time.
- We also recommend that you always use a WIRED connection (Wireless can cause more issues). There are some more networking tips below.
Connecting to Windows XP from a Mac
1. Start at the “Go” drop down menu at the top of your screen, then “Connect to server”.
If the computer you wish to connect to is listed, just select it from the list.
If the computer is not listed, type into the “Server Address” field ’smb://’ followed by the computer name or IP address of the computer to which you want to connect.
Click the “Connect” button in the bottom right corner of the window.
2. Enter in a username and password. If you want the Mac to remember your user name and password combination, check the box “Add to Keychain”.
The workgroup name needs to be the workgroup the PC belongs to. If you don’t know the workgroup that the PC belongs to you can find out by right clicking on the “My Computer” desktop icon on the PC, selecting “Properties” and then selecting the “Computer Name” tab. The workgroup name is about half way down the window.
Click the “OK” button in the bottom right hand corner of the window to finish.
3. Select the “share” you are after. This simply refers to a particular group of shared files. Click “OK”.
4. If successful, the shared files will now appear in a window and an icon link to this share will appear on the desktop.
Best System Admin Tools
TIP: Workaround for Boot Camp insufficient drive space issue
Monday, May 19, 2008
Jim Birkenseer offered a workaround to Friday’s problem of Boot Camp Assistant claiming there isn’t enough drive space to partition a drive, when there actually is. Birkenseer reports:
I had the Boot Camp Insufficient Drive Space Issue just yesterday when installing Win XP Pro SP3 on a Mac mini. I found the workaround at this link. The workaround is a Windows registry thing. The poster of the message claims that the solution is from Microsoft. In case the above link fails for you, here is the solution that worked for me:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetup
3. On the Edit menu, point to New, and click String Value.
4. In the text box under the Name column, type BootDir and press ENTER.
5. Right-click the name BootDir, and then click Modify.
6. In the Edit String Value dialog box, type the drive letter for your system drive, and then click OK. For example, if your system drive is C:, type C:.
7. Close Registry Editor.