Configuration Manager 2012 installation trouble
by Mats Hellman on 26.Jan, 2012 under Uncategorized
I ran into a problem today where the Configuration Manager 2012 RC2 installer would not connect to the database running on the same virtual server. I’ve done more than a few of these installs, without any trouble in the last year so I really wasn’t expecting it.
Anyway the error installing was,
Setup is unable to connect to SQL Server with the connection information provided. Verify following:
Digging trough the installer log I found TCP/IP was disabled so simply enabling the did the trick.
That’s it for now.
Install Software Updates hang on Downloading update
by Mats Hellman on 14.Dec, 2011 under ConfigMgr, Windows 7
Today I ran into an issue where the Build And Capture hung on Downloading update 1. Some googling lead to a known issue in ConfigMGR 2007 SP2 and there is a patch to solve the issue.
http://support.microsoft.com/kb/2509007
Once I installed the patch Software updates were downloaded and installed to the capture computer. This issue seems to affect only Windows 7 captures and with software update packages containing more than 80 patches.
SCCM 2007 management point fails to install
by Mats Hellman on 27.Jul, 2011 under ConfigMgr, Systems Center, Windows
First time I ran in to this problem was in my new virtual test environment. The management point failed to install and MPSetup.log was reporting the WebDav settings were not correct. Looking at them in IIS Manager everything looked just like it should, everything was setup according to the prerequisite document on Technet.
I had to find the problem somewhere else, and I did. Apparently the settings in the GUI didn’t get written to Webdav_schema.xml, and someone was kind enough to document how to change them, so here is the link for future reference.
Setting up Windows Server DHCP for SCCM2007
by Mats Hellman on 27.Jul, 2011 under ConfigMgr, Systems Center, Windows, Windows Deployment
Every now and then I get the question about setting up your DHCP server for SCCM when the DHCP server doesn’t reside on the same host as the SCCM/WDS server.
So to get this working you need to set option 66 and option 67 in your DHCP server.
The options should be set to as following:
Option 66 (boot server host name): IP of your server, ex 10.0.0.1
Option 67 (bootfile name): SMSBoot\boot.sdi
There are many guides out there on this topic, but most don’t need or want to understand the inner workings of DHCP, they just want the filenames. So there you go.
The tale of the broken hard drive
by Mats Hellman on 16.May, 2011 under Linux
About six months ago my trusted Linkstation Live had enough, since late 2008 it has been running without a hitch. The device started blinking red and rebooting it had the nice clicking sound of a broken hard drive.
Nothing was recoverable from the drive so I had to start from scratch, first I went to the local computer store and bought myself an Western Digital Caviar Green 1TB drive.
To get it up and running I had to go trough several pages and try some of the tips from one page and some from another. That’s why I decided to put together my own survival-guide here so I can find it the next time this thing goes south. This quick and dirty howto is for the LS-CHL only!!!
So here it goes:
1. Download the TFTP recovery software from ftp://24.153.165.234/array1/share/nas-recovery/ , if you have the LS-CHL device it’s the TFTP Boot Recovery LS-CHL 1.06 you want.
2. Download the latest firmware from Buffalo, the version 1.07 should be the latest one since they don’t develop it anymore.
3. Disassemble the device, here is a picture of the open device http://www.yamasita.jp/linkstation/2009/09/090912_4l.jpg
4. Next you need a computer running Windows XP, I tried Windows 7 but could not get it to work.
5. Insert the new hard-drive into the Linkstation, you should not partition it. Just put it in.
6. Shut down any firewall service on your Windows XP and set your local IP to 192.168.11.1 and subnet 255.255.255.0. The Linkstation should use 192.168.11.150 once in emergency mode.
7. Unpack the TFTP boot recovery file. And start TFTP Boot.exe file. This should fire up a commandprompt. Look for the line Listening on: 192.168.11.1:69, if it’s there everything should go smoothly from now on.
8. Start the Linkstation and wait for the red light to start flashing, now press the function key for a few seconds and release. The light should turn blue and in your command prompt window you should see the transfer starting.
9. Once the transfer is done start NasNavi.exe to see if your computer can find the device. If it can you can now set your computer to get it’s IP automatically and unpack the Buffalo stock firmware.
10. When you have unpacked the firmware edit the LSUpdater.ini, in the end add
[specialflags]
debug = 1
11. Save and close the LSUpdater.ini file
12. Start the LSUpdater.exe and right click the rings in the upper left corner. Select Debug.
13. Enable all options on the right side of the window and press ok.
14. Start the update.
Wait for a while, quite a while actually and you should have your stock Linkstation Live back. Mine set the language to Japanese but it’s really easy to find the language settings even in Japanese 
If you can’t follow this try googling especially from nas-central.org, this is purely a note for myself in case I ever need to do this again.
