If you want to use the Virtual Machine across all users follw these steps.
1) Logon to system with your User ID.
2) Copy your VM from /Users/< User Name>/Documents/Virtual Machine to Local Mac HDD
3) Right click on .vmwarevm file and select Get Info
4) Click on details in Get info pane
5) From File & Extension remove .vmwarevm extension
6) Now it will show as a folder
7) Right click on Folder and select Get Info
8) Change Group = everyone and Access = Read & Write also others = Read & Write
9) Click on “Apply to enclosed items”
10) System will now prompt for authentication to apply the new permissions please key-in your User id and Password.
11) Change package extension to .vmwarevm
12) Close Get Info window
13) Log off from your account and Login to another Account wherein access has been granted.
14) Launch VMware Fusion Application and run Windows VM from Local Mac HDD
To work around this issue, follow these steps:
Locate the exported virtual machine folder, and then open the .exp file.
In the line between and , delete the GUID. Here is a sample that shows a code example from the .exp file and the value that you should remove:
222dea57-bedd-465c-8fe4-54f2ad7ae699 ** => DELETE THIS GUID**
Save the changes, and then exit Notepad.
Import the modified virtual machine again
I hate installing configuration applications from CD’s that are provided by vendors as they are always bloated and require rbeoots just to do a simple task such as configure a username and password or wireless settings. So if you have Telstra Bigpond 7.2 Wireless Broadband Home Network Gateway and are connected via and ethernet cable, simply login to http://10.0.0.138 with a username of admin and a password of admin and you are then able to manually configure the device with needing to install the software.
I got a refurb Cisco IP Conference Station 7936 the other day, and needed to reconfigure it. I got down into the admin section but could not login as it was asking for a password. I searched around and found that the default password is **#
I hope this helps anybody else who had the same problem.
I had a Dell Precision 390 that I wanted to install Windows 7 on for testing, the only problem was that when I hit F12 to enter the boot menu, the DVD drive was not available as a boot option.
I rebooted, hit F2 and went into the BIOS. I then went down to boot order and the optical drive was showing as not present. I tried to reset to defautls, took the battery out to reset the CMOS, but nothing would make the drive been seen as a bootable device.
I took out the drive and saw that it had been set to MASTER, so I changed it to CABLE SELECT , put it back in and then it was able to be booted from!
We were testing the deployment of a website onto 2 load balanced IIS 7 servers the other day, and the sites were loading fine. the next morning one of the testers was reporting an erorr on the website that said ”Validation of viewstate MAC failed. If this application is hosted by a Web Farm or cluster, ensure that <machineKey> configuration specifies the same validationKey and validation algorithm. AutoGenerate cannot be used in a cluster” . We looked at the error and realised that we need to create a static machinekey and add it into the web.config of both our IIS7 web servers to fix the issue.
We did this, but when we refreshed the page, we were still getting the same error on the website. We tried hitting the sites in new browsers and they loaded fine. What we realised was that becuase we hadn’t shut down the browser, it was still using the old machine key, and as it didn’t match the autogenerated one on the webserver that the browser was hitting, we would get this error.
The steps to fix this are as follows:
1. Generate a new static machinekey and enter it into both web.config files.
2. Open a new browser window to test.
Here is a sample machinekey entry for your web.config file
<machineKey validationKey=’3AE041467624C0947FE562E2DBE6122B532FBC4AA9845AE3D82EC6AC473104EA40A27F8E89BADDAEE44B1F7582FC47299B674ED1FD2DDE1368710504EB2C54C1′ decryptionKey=’2FC79A393A5A463F82D38828F43ED7D030C418B448C9E76C’ validation=’SHA1′/>
I was given a laptop to look at that was coming up with the following error message ” Cannot start Microsoft Office Outlook. Cannot open the Outlook window ” . It would appear that it was going to load then the error would flash up. I went and had a look in the control panel by clicking on the mail icon and checking that there was a correctly configured profile which was true. I decided to make a copy of this profile and see if it would open which it did so what I was dealing with was a corrupt outlook profile.
The fix for this is as follows.
1. Go into control panel then double click the “Mail” icon.
2. Click on “Show Profiles”
3. Click the corrupt profile and click “Copy”
4. Give the profile a name
5. Set it as the default profile
Outlook should now open and you should have access to your emails!
I had to create a new signature for a user with Outlook 2003 the other day, and came across this problem when trying to use the advanced editor. I wanted to add a graphic to the signature, and in Outlook 2003 you have to use the advanced editor to this. The advanced editor opens up whatever program is set to your default HTML editor in Internet settings in the control panel. When you choose the advanced editor, a message pops up saying “this will launch an editor that is not part of Microsoft Outlook” and you can click on yes or no. I clicked on yes , and hour glass appeared and then no editor loaded. I checked task manager and msoxmled.exe and msohtmed.exe were eating up the CPU and when I tried to stop the processes, I couldn’t. I rebooted the PC and tried to edit the signature again, and got the same error.
I thought I would try and change the default HTML editor in “Control Panel” then ”Internet Options” then the ”Programs” tab from Word to Notepad. As soon as I clicked on it, notepad opened up and the html form the signature was there. I decided to try and change it back to Word , and then when I clicked on the advanced editor again, the signature opened up to be edited in Word.
I have no idea why changing the editor type back and forth would fix it, but it worked, and that is all that mattered
After applying SP1 , I kept getting this error in my SCOM monitoring console so I went about trying to fix it.
I wasn’t sure which machine it was that needed to have the agent proxying enabled, so I had to run a query on the database holding the SCOM data to see which computer it was.
1. Copy the string associated with the error – this can be found in the Alert Details under “Alert Description” and will be the 2nd hex string.
2. Run the SQl server management studio and run a query as follows: ( put your copied string in to replace the text below)
select * frombasemanagedentity
where basemanagedentityid = ‘ PUT YOUR STRING IN HERE ’
3. Look at the results from the query and it will tell you the computer name in the Path part of the result.
4. Go back into the SCOM console and click on Administration .
5. Go into Device Management then into Agent Managed and right click on the server that you identified in step 3.
6. Right click on this server, choose Properties then click on the security tab and tick the box. Apply and exit and you shouldn’t see this message again.
The Mac usually takes it’s name form the first person to use it and so if it was me, it would be called “Shnake’s Macbook Pro ” or “Shnake’s Imac” which is better than some generic jumble of letters and numbers, but you still may want to change it.
The way to do this is as follows.
1. Go into System Preferences
2. Click on Sharing ( in the Internet and Network section)
3. Enter the new computer name