Thursday, September 24, 2009

Cannot deploy template: Number of virtual devices exceeds the maximum for a given controller (VMWare ESX vCenter)

If you get this error when trying to deploy a virtual machine from a
template, it could be because you have changed the name of the virtual
machine network, ie. from "VM Network" to something else.

To fix it, do the following:

Convert template to virtual machine.
Edit settings of virtual machine.
Choose correct network for template (it probably shows no name)
Convert virtual machine to template
Try to deploy new virtual machine from template to see if it works
correct again.

Tuesday, September 22, 2009

If you ever get a temporary profile problem

in windows, when the server cannot find a network path to a roaming
profile, it may start to use a temp folder which it will delete after
the user has logged out.

unfortunately, sometimes that lingeres around in server 2008, so what
you will need to do is goto the following key in regedit

hklm->software->microsoft->profilelist

and delete the sid of the user in question. that will be enough to
reset the sid and get the user back up and running

Tuesday, September 08, 2009

WSUS 403 forbidden issue

Hey All,

if you are getting a 403 error when windows clients are attempting to access your local wsus server on 2008 server, it may be due to the fact that during install, the default website was selected as the host for your clients to connect to.

there is nothing wrong with that, unless you have a proxy server setting. if you do, this is where the 403 error comes from.

the way to get around this quite bluntly is to uninstall wsus, reinstall and select to create a new website under the port 8530 - this will work first go, no problems.

also in your wsus GPO, remember that the server name you need to enter is http://hostnameofyourserver.domain.etc:8530

without doing this, your GPO will not work correctly and your clients will also not update!

Monday, September 07, 2009

Quick one! Deploying 2007 office compatibility!

Who knows why the office 2007 compatibility pack is a .exe file and not just an msi.

funnily enough, it does exist though.

download the fileformatconvertors.exe from microsoft (google it!). during the installation, goto the following path:
C:\Program Files\MSECache\O2007Cnv
inside of this you will notice the installation msi - O12Conv.msi

copy this directory and the associated files to your netlogon folder, create a Group policy object as per normal and you're done.