tag:blogger.com,1999:blog-72362771917466788372020-07-22T17:36:09.462-04:00rb303This site is a technical reference site for me and anyone else who finds it. It is not a site for newbies; more for the sysadmin types. This site was created because I was sick of constantly searching for the same information over and over again. It is for me to note things that I want to remember if they come up again.Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.comBlogger34125tag:blogger.com,1999:blog-7236277191746678837.post-90615285008427512852014-05-20T13:52:00.004-04:002014-06-27T11:32:17.800-04:00OS X 10.9.x Trash Deletes Files Immediately on HDD<div class="separator" style="clear: both; text-align: center;"></div><div class="separator" style="clear: both; text-align: center;"><a href="http://4.bp.blogspot.com/-LsMfvCXM3y4/U62OL5PI1WI/AAAAAAABCLg/uShWh9NSFB0/s1600/empty-trash.png" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"><img border="0" src="http://4.bp.blogspot.com/-LsMfvCXM3y4/U62OL5PI1WI/AAAAAAABCLg/uShWh9NSFB0/s1600/empty-trash.png" height="200" width="179" /></a></div>This was a bit annoying, but not game ending. On my "Media HD" any time I would try and delete anything it would delete it instead of putting it in the trash. There appear to be a lot of people that want that feature if you Google around, I however like my trash. The error that pops up is similar to this... "Are you sure you want to delete “XYZ File”?<br /><br />This post on apple support covers it, <a href="https://discussions.apple.com/message/18996316#18996316">https://discussions.apple.com/message/18996316#18996316</a><br /><br />and the resolution is here: <a href="http://www.thexlab.com/faqs/trash.html#Anchor-Files-46919">http://www.thexlab.com/faqs/trash.html#Anchor-Files-46919</a><br /><br /><br /><br /><br />Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-88194106437871028972014-03-31T11:00:00.003-04:002014-06-27T11:34:54.566-04:00Windows Server DHCP 'Enable IP Address Conflict Detection'So this is just a tiny nugget of information for Windows DHCP administrators. You can help mitigate address conflict detection in your dhcp server by setting the following line.<br /><br /><div class="separator" style="clear: both; text-align: center;"><a href="http://4.bp.blogspot.com/-HUvAu1WbdW4/U62O-myM_HI/AAAAAAABCLk/4lPPBXD-268/s1600/WindowsDetectedADuplicateIP.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://4.bp.blogspot.com/-HUvAu1WbdW4/U62O-myM_HI/AAAAAAABCLk/4lPPBXD-268/s1600/WindowsDetectedADuplicateIP.png" /></a></div><br />First you can check if it is enabled or not by running<br /><pre style="background-color: #eaeaea; border: 1px dashed #900; margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">netsh dhcp server show detectconflictretry</pre><br />Then, if it is not enabled you can run<br /><pre style="background-color: #eaeaea; border: 1px dashed #900; margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">netsh dhcp server set detectconflictretry 1</pre><br />Obviously run with 0 to disable.<br /><pre style="background-color: #eaeaea; border: 1px dashed #900; margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">netsh dhcp server set detectconflictretry 0</pre><br />Resources:<br /><a href="http://technet.microsoft.com/en-us/library/dd183587(v=ws.10).aspx">http://technet.microsoft.com/en-us/library/dd183587(v=ws.10).aspx</a>Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-92028922366020064682014-01-11T10:16:00.000-05:002014-06-26T20:48:41.008-04:00Ubuntu slow SSH logonThis is more of an annoyance, but here is a quick and easy fix for a slow ssh logon. The problem is basically when you log in via SSH the password prompt doesn't show up for 10-15 seconds.<br /><pre style="background-color: #EAEAEA; border: 1px dashed #900; margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo nano /etc/nsswitch.conf</pre><br />Now change the line <i>"hosts: files mdns4_minimal [NOTFOUND=return] dns mdns 4 mdns"</i> to <i>"hosts: files dns"</i><br />Log out of your ssh session, and log back in. The password prompt should instantly come up now.Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-38947836457762915992013-09-01T13:56:00.000-04:002014-06-26T20:48:05.923-04:00Ubuntu 12.04 change priority/runlevel of Virtualbox on startupGetting Virtualbox to automatically start seems to be a pretty big problem if you do a search for "virtualbox ubuntu autostart". Most of the issues seem to be stuck at the same part; Vbox runs just fine when running the "vboxautostart-service" but it just will not start when Ubuntu starts. The problem is the runlevels. <br /><br />My problem was at most of my apps were starting at the same exact run level of 20. The problem with that is some should be started before others. For instance, my ZFS needed to load before Vbox, but they were loading at the same time causing Vbox to silently fail. I lowered ZFS to start on 19, and spread out how Vbox starts. They now look like this:<br /><br />S19zfs-mount<br />S19zfs-share<br />S20vboxdrv<br />S21virtualbox<br />S22vboxautostart-service<br />S22vboxballoonctrl-service<br />S22vboxweb-service<br /><br />Notice I have vboxdrv set to start before the rest of the Vbox services. It's pretty simple to change the order, just be careful. First you want to remove the service from update-rc.d, then add it back in with the new order. Here is an example.<br /><br /><pre style="background-color: #eaeaea; border: 1px dashed #900; margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">$sudo update-rc.d -f virtualbox remove</pre><br /><pre style="background-color: #eaeaea; border: 1px dashed #900; margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">$sudo update-rc.d virtualbox defaults 21</pre><br />For more info on run levels in Ubuntu this site is what I used.<br /><br /><a href="http://www.debuntu.org/how-to-managing-services-with-update-rc-d/">http://www.debuntu.org/how-to-managing-services-with-update-rc-d/</a><br /><br />This is the site that pointed me in the correct direction.<br /><br /><a href="http://lifeofageekadmin.com/how-to-set-your-virtualbox-vm-to-automatically-startup/">http://lifeofageekadmin.com/how-to-set-your-virtualbox-vm-to-automatically-startup/</a><br /><br />More reference sites:<br /><br /><a href="https://www.virtualbox.org/manual/ch09.html#autostart">https://www.virtualbox.org/manual/ch09.html#autostart</a>Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-28230613988518580482013-07-24T13:23:00.001-04:002013-07-24T13:28:04.148-04:00Server 2008 WINS with two NIC'sIf you are still running WINS (I do for simplicity) and have two NICs in your WINS box, you will need to change the order of the NICs so WINS knows where to look. This was driving me nuts.<br /><br />Things I did to resolve the issue.<br /><br />DNS Server, on the Interfaces tab disable the NIC your non "main" NICs.<br />NIC, Under "Manage Network Connections" select your non "main' NIC, uncheck all boxes except for IPv4/6. Then select your IPv4 box, uncheck register DNS, and disable NetBIOS.<br />Still in the Manage Network Connections, select Advanced (File Menu) -> Advanced Settings. Move your "main" connection to the top of the list. Press ok.<br /><br />You are done, go back and WINS should know be able to resolve/connect.<br /><br />References:<br /><a href="http://www.pcreview.co.uk/forums/wins-server-defualting-wrong-nic-t1732276.html">http://www.pcreview.co.uk/forums/wins-server-defualting-wrong-nic-t1732276.html</a><br /><br />Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-13155574379292908732013-02-18T14:04:00.000-05:002014-07-21T17:57:08.301-04:00Ubuntu 12.04 + OSX Time MachineI think I have covered this in an old post, but I just fixed some things that have been bugging me. The first referenced article at the bottom was a huge help in getting me started, but he has a lot of malformed xml tags. He also creates 3 files, which I've found you do not need, just create one.<br /><br />Ok, first install netatalk and avahi.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo apt-get install netatalk avahi-daemon</pre><br />Now let's create and edit our new avahi service<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo nano /etc/avahi/services/afp.service</pre><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;"><?xml version="1.0" standalone='no'?><br /><!DOCTYPE service-group SYSTEM "avahi-service.dtd"><br /><service-group><br /> <name replace-wildcards="yes">%h</name><br /> <service><br /> <type>_afpovertcp._tcp</type><br /> <port>548</port><br /> </service><br /> <service><br /> <type>_device-info._tcp</type><br /> <port>548</port><br /> <txt-record>model=Xserve</txt-record><br /> </service><br /> <service><br /> <type>_adisk._tcp</type><br /> <port>9</port><br /> <txt-record>sys=waMA=MM:MM:MM:MM:MM:MM</txt-record><br /> <txt-record>dk0=adVF=0x81,adVN=TimeMachine,adVU=UUUU</txt-record><br /> </service><br /></service-group></pre>If you are running Samba on this server as well, you might want to change the <name> field. I have changed mine to <name>timelord</name>. This will allow your timemachine/apple shares to coexist on the same server (it will look like a different server in Finder though)<br />MM:MM:MM:MM:MM:MM should be the MAC address of your Ubuntu server. You can quickly find it by running the following command.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">ifconfig -a | grep HWaddr</pre>UUUU needs to be a unique UUID. Go to <a href="http://www.guidgen.com/">guidgen.com</a> to generate a UUID. Now save the file, and let's move on.<br /><br />Create some directories and a new user:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo mkdir -p /mnt/timemachine</pre><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo useradd -c "Time Machine User" -d /mnt/timemachine/ -s /bin/false -g 10 timemachine</pre><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo passwd timemachine</pre><br />Set your timemachine share so it is supported:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo touch /mnt/timemachine/.com.apple.timemachine.supported</pre><br />Set some ACLs:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo chown -R timemachine:users /mnt/timemachine</pre><br />Next we move to setting up two files for netatalk:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo nano /etc/netatalk/afpd.conf</pre><br />at the very bottom of the file, add:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">- -tcp -nozeroconf</pre>This tells netatalk to use tcp and not use zeroconf, if you don't use this then you will get two enties in Finder.<br /><br />Configure your /etc/netatalk/AppleVolumes.default file:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;"># By default all users have access to their home directories.<br />#~/ "Home Directory"<br />/mnt/timemachine "TimeMachine" allow:timemachine options:tm<br /># End of File</pre><br />Now restart your services, and you should be done:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo service netatalk restart</pre><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">sudo service avahi-daemon restart</pre><br />References:<br />http://www.64bit.co.uk/index.php/archives/261<br />http://blog.scottlowe.org/2009/01/02/ubuntu-and-mac-os-x-integration/<br />http://derekingrouville.ca/2011/ubuntu-time-machine-server-for-osx-lion/<br />http://www.bootc.net/archives/2010/11/07/apple-time-machine-and-netatalk/ <br />http://netatalk.sourceforge.net/wiki/index.php/Bonjour_record_adisk_adVF_values<br /><a href="https://developer.apple.com/library/mac/#documentation/NetworkingInternetWeb/Conceptual/TimeMachineNetworkInterfaceSpecification/TimeMachineRequirements/TimeMachineRequirements.html">Time Machine Server Requirements</a>Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-59165393585853812522012-06-18T20:03:00.000-04:002012-06-23T00:32:51.852-04:00Ubuntu Server 12.04 LTS RocketRaid 26xx DKMS DriverFirst, grab the build tools and dkms:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;"><span style="font-size: x-small;">sudo apt-get install build-essential dkms libwww-perl</span></pre><br />Download the driver source from Highpoint:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; word-wrap: break-word;"><span style="font-size: x-small; white-space: pre-wrap;">lwp-download </span><span style="background-color: transparent; white-space: pre-wrap;"><span style="font-size: x-small;">http://www.highpoint-tech.com/BIOS_Driver/rr26xx/2640X1-2640X4-2642/Linux/rr264x-linux-src-v1.4-120524-1520.tar.gz</span></span></pre><br />Extract the tar:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; word-wrap: break-word;"><span style="font-size: x-small; white-space: pre-wrap;">tar -zxvf </span><span style="background-color: transparent; font-size: x-small; white-space: pre-wrap;">rr264x-linux-src-v1.4-120524-1520.tar.gz</span><span style="font-size: x-small; white-space: pre-wrap;"><br />cd </span><span style="background-color: transparent; white-space: pre-wrap;"><span style="font-size: x-small;">rr264x-linux-src-v1.4</span></span></pre><br />Create the DKMS configuration file:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;"><span style="font-size: x-small;">cat >dkms.conf</span></pre><br />Cut and Paste the following text:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;"><span style="font-size: x-small;">MAKE="make -C product/rr2640/linux KERNDIR=/lib/modules/${kernelver}/build"<br />CLEAN="make -C product/rr2640/linux/ clean"<br />BUILT_MODULE_NAME=rr26xx<br />DEST_MODULE_LOCATION=/kernel/drivers/scsi/<br />BUILT_MODULE_LOCATION=product/rr2640/linux/<br />PACKAGE_NAME=rr264x<br />PACKAGE_VERSION=1.4<br />AUTOINSTALL=yes<br />REMAKE_INITRD=yes</span></pre>Hit "Control-D" (as in Delta) to close the file.<br /><br />Run these commands:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;"><span style="font-size: x-small;">sudo cp -R . /usr/src/rr264x-1.4<br />sudo dkms add -m rr264x -v 1.4<br />sudo dkms build -m rr264x -v 1.4<br />sudo dkms install -m rr264x -v 1.4</span></pre><br />That should be it, I have not tested this from scratch. There are possibly steps missing, but until I have a clean system to test this is all I have for now.<br /><br />References:<br /><span style="font-size: x-small;">Major help from CharlesA on the Ubuntu forums <a href="http://ubuntuforums.org/showpost.php?p=12014967&postcount=8">http://ubuntuforums.org/showpost.php?p=12014967&postcount=8</a></span>Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-90785896266533889892012-06-09T13:29:00.001-04:002012-06-18T11:11:29.907-04:00Mythbuntu 12.04 MythTV audio buffering issueI was noticing in my mythfrontend logs, this warning:<br /><pre style="background-color: #ffffff; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">ALSA: Setting hardware audio buffer size to 128<br />ALSA: Error opening /proc/asound/card2/pcm9p/sub0/prealloc: Permission denied.<br />ALSA: Try to manually increase audio buffer with: echo 128 | sudo tee /proc/asound/card2/pcm9p/sub0/prealloc<br />ALSA: Unable to sufficiently increase ALSA hardware buffer size - underruns are likely</pre><br />I've read in multiple places that as long as you have sound, and no problems it is safe to ignore. But I personally do not like to see random errors. There was a reason that the developers are telling you to manually run that line. So... off searching I did. I read in a few places that your user account (the main account you log into MythTV with) should be part of the audio group, welp simple enough run<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo usermod -a -G audio username</pre><br />But, that doesn't seem to be good enough. It appears that the /proc/asound directory's are all owned by root. So if I do a little chown -R root:audio /proc/asound; bam the error is gone. But if I reboot that front end, it resets it back to root:root. So I need to make the change stick on startup.<br /><br />First I wrote a small script that will make the change, and make it stick on reboot. I put all my scripts in one place in my home directory called "scripts" (witty, I know).<br />So I created a file called ~/scripts/asound.sh<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">nano ~/scripts/asound.sh</pre><br />Then I add...<pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); color: #333333; line-height: 18px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">#!/bin/sh<br />/bin/chmod -R ug+rw /proc/asound<br />/bin/chown -R root:audio /proc/asound<br />exit 0</pre><br />Let's make that file executable<pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); color: #333333; line-height: 18px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">chmod +x ~/scripts/asound.sh</pre><br />Now add this to /etc/rc.local<pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); color: #333333; line-height: 18px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">/home/username/scripts/asound.sh</pre><br />This has solved one of my issues where one of my front end's would stutter when you were on the guide screen, and scrolling up/down.Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-72422714533016456382011-12-15T13:01:00.002-05:002013-08-10T15:17:41.140-04:00Ubuntu Adding Samba Users and GroupsI will be adding users to both my Ubuntu Server, then create their samba user counterpart.<br /><br />First we need to add a group for our users to join.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo groupadd smbusers</pre><br />Then we need to use the useradd command to add new users to the group we just created (or any existing group); and add the user to the system. The syntax is "useradd -G {group-name} username"<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo useradd -G smbusers username<br />sudo passwd username (optional)<br />sudo smbpasswd -a username</pre><br />If you already have a user that is created and want to add them to a group, you can do this.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo usermod -a -G smbusers username</pre><br />References:<br /><a href="http://www.cyberciti.biz/faq/adding-a-user-to-a-samba-smb-share/">http://www.cyberciti.biz/faq/adding-a-user-to-a-samba-smb-share/</a><br /><a href="http://www.cyberciti.biz/faq/howto-linux-add-user-to-group/">http://www.cyberciti.biz/faq/howto-linux-add-user-to-group/</a>Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-27687921316739073592011-12-15T12:21:00.001-05:002012-06-05T15:28:04.236-04:00Ubuntu Server 10.04 LTS NIC Bonding (updated for 12.04)First let's install ifenslave, this is required to bond the nic's.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo apt-get install ifenslave</pre><br />Then we need to edit /etc/network/interfaces<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo nano /etc/network/interfaces</pre><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;"># This file describes the network interfaces available on your system<br /># and how to activate them. For more information, see interfaces(5).<br /><br /># The loopback network interface<br />auto lo<br />iface lo inet loopback<br /><br /># The primary network interface<br />#auto eth0<br />#iface eth0 inet dhcp<br /><br /># This section works for 10.04<br />#auto bond0<br />#iface bond0 inet static<br />#address xxx.xxx.xxx.xxx<br />#gateway xxx.xxx.xxx.xxx<br />#netmask xxx.xxx.xxx.xxx<br />#bond-slaves eth0 eth1<br /># LACP confuration<br />#bond_mode 802.3ad<br />#bond_miimon 100<br />#bond_lacp_rate 1<br /><br /># This section works for 12.04<br />auto eth0<br /> iface eth0 inet manual<br /> bond-master bond0<br /><br />auto eth1<br /> iface eth1 inet manual<br /> bond-master bond0<br /><br />auto bond0<br />iface bond0 inet static<br />address xxx.xxx.xxx.xxx<br />gateway xxx.xxx.xxx.xxx<br />netmask xxx.xxx.xxx.xxx<br /># LACP confuration<br />bond-mode 802.3ad<br />bond-miimon 100<br />bond-lacp_rate 1<br />bond-slaves none<br /></pre>*<strong>NOTE</strong>* If you only have 2 NIC's and want them bonded comment out your eth0 lines<br /><br />Next update your resolv.conf so you have DNS; edit /etc/resolvconf/resolv.conf.d/head <pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo nano /etc/resolvconf/resolv.conf.d/head<br />nameserver xxx.xxx.xxx.xxx<br />nameserver xxx.xxx.xxx.xxx<br />search domain.name<br /></pre><br />Restart network services<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo /etc/init.d/networking restart</pre><br />*<strong>NOTE</strong>* Here is info about different bonding modes:<br />mode=0 (balance-rr) Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.<br /><br />mode=1 (active-backup) Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond’s MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode.<br /><br />mode=2 (balance-xor) XOR policy: Transmit based on [(source MAC address XOR'd with destination MAC address) modulo slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance.<br /><br />mode=3 (broadcast) Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.<br /><br />mode=4 (802.3ad) IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.<br /><br />* Pre-requisites:<br />* Ethtool support in the base drivers for retrieving the speed and duplex of each slave.<br />* A switch that supports IEEE 802.3ad Dynamic link aggregation. Most switches will require some type of configuration to enable 802.3ad mode.<br /><br />mode=5 (balance-tlb) Adaptive transmit load balancing: channel bonding that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.<br /><br />* Prerequisite: Ethtool support in the base drivers for retrieving the speed of each slave.<br /><br />mode=6 (balance-alb) Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server.<br /><br />References:<br /><a href="https://help.ubuntu.com/community/UbuntuBonding">https://help.ubuntu.com/community/UbuntuBonding</a><br /><a href="http://www.ubuntugeek.com/how-to-setup-bond-or-team-network-cards-in-ubuntu-10-1010-04.html">http://www.ubuntugeek.com/how-to-setup-bond-or-team-network-cards-in-ubuntu-10-1010-04.html</a>Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-79495719027943406542011-12-15T10:53:00.004-05:002012-04-27T00:53:27.679-04:00Ubuntu Server 10.04 LTS RocketRaid 26xx DKMS DriverFirst, install the build tools:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo apt-get install build-essential</pre><br />Download the driver source from Highpoint:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">lwp-download http://www.highpoint-tech.com/BIOS_Driver/rr26xx/2640X1-2640X4-2642/Linux/rr264x-linux-src-v1.3-legacy_single-101203-0910.tar.gz</pre><br />Extract the tar:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">tar -zxvf rr264x-linux-src-v1.3-legacy_single-101203-0910.tar.gz<br />mv rr2640-linux-src-v1.3-legacy_single rr26xx-linux-src-v1.3<br />cd rr26xx-linux-src-v1.3</pre><br />Make sure DKMS is installed:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo aptitude install dkms</pre><br />Create the DKMS configuration file:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">cat >dkms.conf</pre><br />Cut and Paste the following text:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">MAKE="make"<br />BUILT_MODULE_NAME=rr26xx<br />DEST_MODULE_LOCATION=/kernel/drivers/scsi<br />PACKAGE_NAME=rr26xx<br />PACKAGE_VERSION=1.3<br />AUTOINSTALL=yes<br />POST_BUILD="do_Module.symvers rr26xx save $dkms_tree/$module/$module_version/build/Module.symvers"<br />REMAKE_INITRD=yes</pre>Hit "Control-D" (as in Dog) to close the file.<br /><br />Copy the Makefile and Config files up to the top directory:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">cp product/rr2640/linuxls/* .<br />mv Makefile Makefile_orig</pre><br />Modify the HPT_ROOT in the Makefile:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sed 's/HPT_ROOT := ..\/..\/../HPT_ROOT := \/var\/lib\/dkms\/rr26xx\/1.3\/build/' Makefile_orig >Makefile</pre><br />Move the source into /usr/src for DKMS:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">cd ..<br />sudo mv rr26xx-linux-src-v1.3 /usr/src/rr26xx-1.3</pre><br />Trick dkms into looking in the /usr/src directory for the precompiled RocketRaid object code:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">mv /usr/src/rr26xx-1.3/lib /usr/src/rr26xx-1.3/real_lib<br />ln -s /usr/src/rr26xx-1.3/real_lib /usr/src/rr26xx-1.3/lib</pre>*<strong>NOTE</strong>* For some reason dkms will not copy object files (.o) when doing builds, so we need to fool it.<br />*<strong>NOTE</strong>* Above symbolic link must be complete (absolute) path!<br /><br />Add the source to DKMS:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo dkms add -m rr26xx -v 1.3</pre><br />Build the module:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo dkms build -k `uname -r` -m rr26xx -v 1.3</pre>*<strong>NOTE</strong>* This should hopefully compile correctly. If not, you can view the log output from the file "/var/lib/dkms/rr26xx/1.3/build/make.log"<br /><br />Next install the module:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo dkms install -k `uname -r` -m rr26xx -v 1.3</pre><br />Finally, create the boot image:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo mkinitramfs -o /boot/initrd.img-`uname -r` `uname -r`</pre><br />*<i>UPDATE</i>* I just verified that this will make it through a kernel update. I just updated my server to 2.6.32-37-server and rebooted, my card was detected, and the raid array was intact.<br /><br />References:<br />This is adapted from <a href="https://help.ubuntu.com/community/RocketRaid#RocketRaid_26xx_Driver">https://help.ubuntu.com/community/RocketRaid#RocketRaid_26xx_Driver</a><br />with support from this forum <a href="http://ubuntuforums.org/showthread.php?t=1633597">http://ubuntuforums.org/showthread.php?t=1633597</a>Aaronhttp://www.blogger.com/profile/15971698658561391500noreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-81339779849582511182011-09-26T14:43:00.002-04:002011-09-26T14:43:38.459-04:00Mythbuntu: Antec Fusion v1 VFD & MCE Remote (Updated for 10.10)This is an updated how-to of <a href="http://www.maistech.net/2009/11/mythbuntu-antec-fusion-v1-vfd-mce.html">my notes</a> from an earlier post. Things have changed since Ubuntu 9.04, I am now on 10.10 due to the inclusion of Trim support. The mceusb remote should just work out of the box. <a href="http://wilsonet.com/?page_id=95">Here are some notes on it</a>. So basically this is to get your Antec Fusion v1 VFD working.<br /><a name='more'></a><br />My install notes:<br /><br />Install lcdproc and lirc (lirc should already be installed, but just incase)<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo apt-get install lcdproc lirc</pre><br />Create a file /etc/modprobe.d/imon-vfd.conf; add the following line.<br />(This is to pass kernel options at bootup. This is for my VFD, the later version VFD's are diferent. References at end of article)<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">options lirc_imon display_type=1</pre><br />Edit /etc/LCDd.conf<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">Driver=imon<br />Goodbye=""<br />ServerScreen=blank<br /></pre><br />Edit /etc/lirc/lircd.conf add line at end <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">include "/usr/share/lirc/remotes/imon/lircd.conf.imon-knob"</pre><br />Restart lirc<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo service lirc restart</pre><br /><br />NOTE: If you are using XBMC, edit your ~/.xbmc/userdata/guisettings.xml so that < haslcd> is set to true<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">nano +1892 ~/.xbmc/userdata/guisettings.xml</pre>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-69369026678900561582011-09-26T01:34:00.001-04:002011-09-26T14:44:29.618-04:00Mythbuntu: MythTV/XBMC SwitchingThis script allows switching between mythtv frontend and xbmc. After you have lirc and irexec installed and running.<br /><br />http://code.google.com/p/yatvgrabber/wiki/XbmcMythtvRemote<br /><br />To stop Mythfrontend from automatically starting on reboot, this is how I removed it.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">cd .config/autostart<br />rm mythtv.desktop</pre>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-70916438926716017372011-09-25T19:26:00.000-04:002011-12-15T12:42:57.874-05:00Ubuntu Server 10.04 LTS Allowing Symlinks with Samba<br />Apparently in 10.04 you need to add a few lines to allow symlinks in your samba share. I kept getting access denied in Windows.<br /><br />Under Global, add the following 3 lines:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">[global]<br />follow symlinks = yes<br />wide links = yes<br />unix extensions = no</pre><br />Now restart Samba<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo /etc/init.d/smbd restart</pre><br />You should be good to go!Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-38827182764122252692011-09-25T03:02:00.003-04:002012-05-02T10:33:16.397-04:00Ubuntu 10.04 LTS bootable software RAID-1Start from your home directory<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">cd ~</pre><br />Install mdadm<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo apt-get install mdadm</pre><br />You need 2 modules loaded, md and raid1 Ubuntu 10.04 should automatically have md loaded. You can verify this by running "fgrep CONFIG_MD /boot/config-$(uname -r)"<br /><br />We need to load the raid1 module so when you reboot it will load.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo echo raid1 >> /etc/modules</pre><br />Now we will load it manually so we don't have to reboot<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo modprobe raid1</pre><br />Verify its loaded<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">lsmod | grep raid1</pre><br />Next we are going to copy the partition info from sda to sdb.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo sfdisk -d /dev/sda > sda.out<br />sudo sfdisk -f /dev/sdb < sda.out</pre>*<strong>NOTE</strong>* If you get "I don't like these partitions – nothing changed." Verify it by comparing the output of sfdisk -l /dev/sda and sfdisk -l /dev/sdb.<br /><br />Change the partition type of the /dev/sdb Linux partition(s) to "Linux raid autodetect"<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo sfdisk --change-id /dev/sdb 1 fd</pre><br />Now we're ready to create the array. We specify a RAID 1 array with 2 devices. The first drive is missing (we add it later) and the second is /dev/sdb1:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo mdadm --create /dev/md0 --level=1 --raid-devices=2 missing /dev/sdb1</pre><br />Now, we need to create and update the mdadm.conf.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo cp /etc/mdadm/mdadm.conf /etc/mdadm/mdadm.bak && sudo cp /etc/mdadm/mdadm.conf mdadm.conf && sudo mdadm --detail --scan >> mdadm.conf && sudo cp mdadm.conf /etc/mdadm/mdadm.conf</pre>*<strong>NOTE</strong>* It will put in a parameter metadata=00.90 that will cause warnings later. Apparently, this is a bug and it is safe to remove it.<br /><br />Now, we format the raid volume<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo mkfs -t ext4 /dev/md0</pre><br />Find out the UUID of the array<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo blkid</pre><br />Make a copy of /etc/fstab in your home directory and change root to mount to the UUID of the array. Don't change the real /etc/fstab quite yet.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo cp /etc/fstab /etc/fstab.bak && sudo cp /etc/fstab fstab && sudo nano fstab</pre><br />Really quick, check what kernel you are running you will need this for the next section.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">uname -r</pre><br />Next is adding a custom GRUB2 setup<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo cp /etc/grub.d/40_custom 09_swraid1_setup && sudo nano 09_swraid1_setup</pre><br />Replace "2.6.32-36-server" with your kernel version you got from running "uname -r"<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">menuentry 'Ubuntu, with Linux 2.6.32-36-server' --class ubuntu --class gnu-linux --class gnu --class os {<br /> recordfail<br /> insmod raid<br /> insmod mdraid<br /> insmod ext2<br /> set root='(md0)'<br /> linux /boot/vmlinuz-2.6.32-36-server root=/dev/md0 ro quiet<br /> initrd /boot/initrd.img-2.6.32-36-server<br />}</pre><br />Now copy both files we just created to their respective locations<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo cp fstab /etc/ && sudo cp 09_swraid1_setup /etc/grub.d/</pre><br />Let's update Grub<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo update-grub && sudo update-initramfs -u</pre><br />And make sure Grub is installed on both drives<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo grub-install /dev/sda && sudo grub-install /dev/sdb</pre><br />Create a directory called "tmpraid"<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo mkdir /tmpraid</pre><br />Mount the array on /tmparray<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo mount /dev/md0 /tmpraid && sudo rsync -vaxP / /tmpraid</pre><br />Reboot...<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo reboot</pre><br />Change the partition type of sda now<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo sfdisk --change-id /dev/sda 1 fd</pre><br />Add it to the array:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo mdadm --add /dev/md0 /dev/sda1</pre><br />Let's watch /dev/sda sync:<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">watch cat /proc/mdstat</pre><br />Let's delete the GRUB entry we created earlier since it is no longer needed<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo rm -f /etc/grub.d/09_swraid1_setup</pre><br />Now let's finish up<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo update-grub && sudo update-initramfs -u</pre><br />Now we're done, reboot and test if you so wish. <br /><br />References:<br /><a href="http://www.jfamiglietti.com/john/?p=152">http://www.jfamiglietti.com/john/?p=152</a> <br /><a href="http://linuxconfig.org/Linux_Software_Raid_1_Setup">http://linuxconfig.org/Linux_Software_Raid_1_Setup</a>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-13485774482523549882011-09-24T11:13:00.000-04:002011-09-26T01:44:25.405-04:00Disable/Enable Windows IPv6 Tunnels<span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;">I just found this link, and wanted to preserve it. Very nice for disabling IPv6 tunnels on Windows machines. I am running dual-stack, and the tunnels felt like they were in the way.</span><br /><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><br /></span><br /><span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif;"><a href="http://support.microsoft.com/kb/929852">http://support.microsoft.com/kb/929852</a></span>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-42043576902159561382011-09-24T11:10:00.002-04:002011-09-26T01:43:32.702-04:00Windows Disable IPv6 RA solicitations<br />This works for both Windows 7 and Server 2008, I use this if I have set a static IPv6 address and want to stop the Windows box from having more than one IPv6 address.<br /><br />First we want to find the index value of your nic.<br /><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">c:\netsh int ipv6 sh int<br />Idx Met MTU State Name<br />--- ---------- ---------- ------------ ---------------------------<br /> 1 50 4294967295 connected Loopback Pseudo-Interface 1<br /> 11 10 1500 connected Local Area Connection<br /></pre><br />Now apply the value to disable the RA solicitation<br /><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">c:\netsh int ipv6 set int 11 routerdiscovery=disabled<br /></pre><br />Now after a reboot you should only have one IPv6 IP address.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-68903792533811035912010-01-20T22:21:00.002-05:002014-10-12T13:29:51.703-04:00Terminal Server 2003 msiexec high cpu usage, hp updOk, so this has been killing me for a while. I have a terminal server that was unable to add/remove applications in a timely manor; when I say timely, I mean TIMELY! It could take days to install Office, or HOURS to install a security patch.<br /><br />I still haven't fully isolated what causes the problem to start (possibly bad printer driver). But this solution worked for me this time.<br /><br />I removed these Registry Keys; which were full of HP garbage.<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">[HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\RefHive\Hewlett-Packard]<br />[HKEY_USERS\.DEFAULT\Software\Hewlett-Packard]<br />[HKEY_CURRENT_USER\Software\Hewlett-Packard]</pre><br />I then made sure that there were no Universal Print monitors. <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: no-wrap; word-wrap: normal;">[HLKM\SYSTEM\CONTROLSET001\CONTROL\Print\Monitors]<br />[HLKM\SYSTEM\CURRENTONTROLSET\CONTROL\Print\Monitors]</pre><br /><br />References:<br />http://forums11.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1247687<br />http://forums11.itrc.hp.com/service/forums/bizsupport/questionanswer.do?admit=109447626+1264044137399+28353475&threadId=968215Unknownnoreply@blogger.com3tag:blogger.com,1999:blog-7236277191746678837.post-10293119579439531002009-12-08T09:09:00.001-05:002011-09-26T01:35:54.306-04:00Managing Printers: Kernel Mode Drivers (version 2) are blocked on the target machineWhen trying to restore printers using Printer Migrator on a windows 2003 server, you may receive this message: “WARNING: Kernel Mode Drivers (version 2) are blocked on the target machine. Disable Kernel Mode driver blocking and re-run Printer Migrator…”<br /><br />1. Run Local Group Policy. Open Run and type gpedit.msc<br />2. Explorer Computer Configuration,<br />3. Select Administrative Templates, <br />4. click Printer.<br />5. On the Right pane, right-click on "Disallow installation of printers using kernel mode drivers"<br />6. Select Properties and check Disabled.<br />7. Click OK to close the Local Group Policy.Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-77455489037839108322009-11-30T14:40:00.000-05:002009-11-30T14:40:54.318-05:00Terminal Server LicensingThis is a pretty basic one today, but I thought it would be worth noting. In a domain if you want to use Terminal Server licensing on a local server instead of the auto-detected server follow this guide: <a href="http://support.microsoft.com/kb/279561">http://support.microsoft.com/kb/279561</a><br /><br />To tighten security on that server so other Terminal Servers can not use your licenses<br />gpedit.msc<br />goto "Computer Configuration\Administrative Templates\Windows Components\Terminal Services\TS Licensing"<br />Enable "License server security group"<br />Add your Terminal Server on the Licensing server to the "Terminal Server Computers" group.<br /><br />References:<br /><a href="http://support.microsoft.com/kb/279561">http://support.microsoft.com/kb/279561</a><br /><a href="http://technet.microsoft.com/en-us/library/cc725704(WS.10).aspx">http://technet.microsoft.com/en-us/library/cc725704(WS.10).aspx</a><br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-22754959526683707262009-11-29T15:39:00.008-05:002010-01-12T13:36:06.564-05:00Mythbuntu: Firewire Channel and Recording<br />I got this working, and it was helluva lot simpler than I had been going after. There were a few key settings that made everything just fall into place and "just work".<br />First and foremost find out what works best for YOUR STB. From everything I've read Motorola's like Broadcast @ 400mbps. Most articles I've read tell you use Point to Point (P2P), this failed every single time for me. So Broadcast and 400mbps (this is in back end settings for your device).<br />That is really all I needed to do to get it working, but here are my notes on if it does fail how you can prime the STB.<br /><a name='more'></a><br />Notes:<br />First we need to grab some files to build "firewire_tester"<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo apt-get install libiec61883-dev build-essential libraw1394-dev libiec61883-dev libavc1394-dev wget</pre><br />Next we want to change to /usr/local/bin then grab firewire_tester.c<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">cd /usr/local/bin<br />sudo wget "http://cvs.mythtv.org/trac/browser/trunk/mythtv/contrib/development/firewire_tester/firewire_tester.c?format=txt" -O firewire_tester.c </pre><br />Let's compile firewire_tester.c<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">gcc -Wall -o firewire_tester firewire_tester.c -liec61883 -lraw1394</pre><br />Now we have to make firewire_primer.pl executable<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo chmod +x /usr/share/doc/mythtv-backend/contrib/user_jobs/firewire_primer.pl</pre><br />Create a link to firewire_primer.pl (should still be in /usr/local/bin)<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo ln -s /usr/share/doc/mythtv-backend/contrib/user_jobs/firewire_primer.pl firewire_primer.pl</pre><br />Test your connection (should not have TV on while doing this)<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo ./firewire_primer.pl</pre><br />References:<br /><div><a href="http://www.mythtv.org/wiki/Firewire_Priming#One_Tuner_Priming_Script" target="_blank">http://www.mythtv.org/wiki/<wbr></wbr>Firewire_Priming#One_Tuner_<wbr></wbr>Priming_Script</a><br /></div><a href="http://www.mythtv.org/wiki/User:Yeffetn" target="_blank">http://www.mythtv.org/wiki/<wbr></wbr>User:Yeffetn</a><br />https://wiki.ubuntu.com/majoridiot<br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-33515078980262141892009-11-29T14:15:00.013-05:002011-02-12T18:31:22.520-05:00Mythbuntu: Antec Fusion v1 VFD & MCE RemoteI like simple. But in trying to get my VFD and MCE remote working seemed anything but. So this is how I got my VFD and MCE remote working. This is pretty strait forward, I tried all sorts of articles but all in all, if you are running 0.22 this is what I came up with.<br /><a name='more'></a><br />My install notes:<br /><br />Install lcdproc and lirc (lirc should already be installed, but just incase)<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo apt-get install lcdproc lirc</pre><br />Create a file /etc/modprobe.d/imon-vfd.conf; add the following line.<br />(This is to pass kernel options at bootup. This is for my VFD, the later version VFD's are diferent. References at end of article)<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">options lirc_imon display_type=1</pre><br /><s>0.22 default you need to run a mysql query due to bug (link bug)</s><br /><s>at the end where it says "null", you can also put your hostname there, i've tried both, either works.</s><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;"><s>mysql -u mythtv -p [enter password]<br />use mythconverg;<br />insert into settings (value,data,hostname) values ('LCDServerHost','127.0.0.1', null); </s></pre><br />Edit /etc/LCDproc.conf<br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">Driver=imon<br />Goodbye=""<br />ServerScreen=blank<br /></pre><br />Edit /etc/lirc/lircd.conf add line at end <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">include "/usr/share/lirc/remotes/imon/lircd.conf.imon-mceusb"</pre><br /><s>Not really sure if this is needed, but it works so...</s><br /><s>Create lirc.custom file in init.d</s><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;"><s>sudo /usr/sbin/lircd --driver=default --device=/dev/lirc0 --pidfile=/var/run/lirc0.pid --listen=8765<br />sudo /usr/sbin/lircd --driver=default --device=/dev/lirc1 --pidfile=/var/run/lirc1.pid --output=/dev/lircd --connect=localhost:8765</s></pre><s>Save file</s><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;"><s>sudo chmod +x lirc.custom</s></pre><s><br /></s><br /><s>Test and see if MCE remote is working; if it is, cd /etc/init.d</s><br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;"><s>sudo update-rc lirc.custom defaults</s></pre><br /><br /><div style="margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px;">Edit /etc/lirc/hardware.conf change</div><div style="margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px;"></div><pre style="background-color: #f0eee6; border-bottom-color: rgb(193, 180, 150); border-bottom-style: dashed; border-bottom-width: 1px; border-left-color: rgb(193, 180, 150); border-left-style: dashed; border-left-width: 1px; border-right-color: rgb(193, 180, 150); border-right-style: dashed; border-right-width: 1px; border-top-color: rgb(193, 180, 150); border-top-style: dashed; border-top-width: 1px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 4pt; padding-left: 4pt; padding-right: 4pt; padding-top: 4pt; white-space: pre-wrap; word-wrap: break-word;">REMOTE_DEVICE="/dev/lirc0"</pre>to<br /><div style="margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px;"></div><pre style="background-color: #f0eee6; border-bottom-color: rgb(193, 180, 150); border-bottom-style: dashed; border-bottom-width: 1px; border-left-color: rgb(193, 180, 150); border-left-style: dashed; border-left-width: 1px; border-right-color: rgb(193, 180, 150); border-right-style: dashed; border-right-width: 1px; border-top-color: rgb(193, 180, 150); border-top-style: dashed; border-top-width: 1px; margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px; padding-bottom: 4pt; padding-left: 4pt; padding-right: 4pt; padding-top: 4pt; white-space: pre-wrap; word-wrap: break-word;">REMOTE_DEVICE="/dev/lirc1"</pre><div><br /></div><br /><div style="margin-bottom: 0px; margin-left: 0px; margin-right: 0px; margin-top: 0px;"><br /></div><br />References: <br />http://www.gossamer-threads.com/lists/mythtv/users/402902Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-32491104598505058172009-11-28T12:33:00.035-05:002009-11-29T23:18:40.780-05:00Mythbuntu: Mounting MediaI was going to write up a long nice detailed thing here, but then I found this, <a href="https://help.ubuntu.com/community/MountWindowsSharesPermanently">https://help.ubuntu.com/community/MountWindowsSharesPermanently</a> and now I don't need to as it explains it way better.<br /><a name='more'></a><br />My quick notes: <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo apt-get install smbfs</pre><br />Find my UID <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">id</pre><br />Create my /etc/samba/cifspw file <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">username=MyUsername<br />password=MyPassword</pre><br />My fstab lines <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">//syndrome/movies /home/mediacenter/Movies cifs uid=1000,gid=1000,credentials=/etc/samba/cifspwd,domain=incredibles 0 0<br />//syndrome/music /home/mediacenter/Music cifs uid=1000,gid=1000,credentials=/etc/samba/cifspwd,domain=incredibles 0 0<br />//syndrome/pictures/iPhoto\040Library/data /home/mediacenter/Pictures cifs uid=1000,gid=1000,credentials=/etc/samba/cifspwd,domain=incredibles 0 0</pre><br />Create mount directory <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">mkdir /home/mediacenter/Movies</pre><br />Test mount <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">cd /home/mediacenter/<br />sudo mount -a Movies</pre><br />Set permissions on folder <br /><pre style="background-color: #f0eee6; border: 1px dashed rgb(193, 180, 150); margin: 0px; padding: 4pt; white-space: pre-wrap; word-wrap: break-word;">sudo chown mediacenter:mediacenter Movies<br />sudo chmod 755 Movies/</pre><br />Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-52853944513273706442009-11-18T18:09:00.004-05:002009-11-30T01:05:33.317-05:00Ubuntu 9.10 Remix Frustration<div style="font-family: inherit;"><span style="font-size: small;">Ok, so I downloaded Ubuntu 9.10 Remix; burned it; installed it. All flawlessly on my Dell 700m. This laptop is old, Pentium M 1.8; 2GB Ram, 60 GB Hard Drive. Yes, I know this is a old laptop, but honestly it does everything that a "Netbook" does 12.1" 1280x800 screen, DVD Burner.. OK battery life.</span><br /></div><div style="font-family: inherit;"><br /></div><div style="font-family: inherit;"><span style="font-size: small;">So, I installed Remix, and everything went as expected except that I can't use it. It seems that the Intel 852/855 Video chipset doesn't properly work due to the "fancy" video rendering Remix uses.</span><br /></div><div style="font-family: inherit;"><br /></div><div style="font-family: inherit;"><span style="font-size: small;">I doubt anyone is reading this, but if you have a possible solution I would be glad to hear it. From what I can tell I think Remix is perfect for this laptop so ...</span><br /></div>Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-7236277191746678837.post-57193081374188712322009-09-22T14:37:00.004-04:002009-11-30T00:51:45.838-05:00Change the default location of the user profiles in Windows 2003 Server<div style="font-family: inherit;"><span style="font-size: small;">Goal is to define an alternate location for user profiles; move them from the C: drive to a different drive due to space allocation. I want to store the terminal server profiles on a different drive.</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">In the registry find:</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">ProfilesDirectory:C:\Documents and Settings</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Change to:</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">ProfilesDirectory:X:\Documents and Settings</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">**Note** Existing Profiles will remain under C:\Documents And Settings; you'll need to move these profiles manually.</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">New users will have there profile created in the location you specified.</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">There is also an administrative template which enables you to set the default place teminal server profiles. You can find this template at following location in the group policy editor:</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Computer Configuration\Administraive Templates\Windows Components\Terminal Services\Set Path for TS Roaming Prifiles.</span><br /></div><a name='more'></a><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Next is to move the existing profiles to the new path X:\Documents and Settings\</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">To rename (or move) the User Profile folder, you may use the following method. This method has been adopted from KB314843, but this page explains in detail how to rename an User account home directory.</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">**NOTE** Though you can move or rename the user profile folder, there may be some side effects after using this method. This is because of the reason that there may be some absolute path references (to the old user profile folder) in the registry added by third-party software. Therefore, there may be a loss of functionality in the respective applications.</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Rename the User Profile folder using Windows Explorer</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Logon to an admin account that is not the account being renamed. </span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Open the Documents and Settings folder, by typing this in Start, Run dialog: </span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">%systemdrive%\Documents and Settings</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">The list of folders will be displayed. Select the corresponding folder of the user account that you want to rename. </span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Example:</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">%SystemDrive%\Documents and Settings\OldUsername</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">becomes</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">%SystemDrive%\Documents and Settings\NewUsername</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Next step is to notify the system that the user profile path has changed.</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Changing the ProfileImagePath value in the registry</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">ProfileImagePath registry value</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">The ProfileList registry key contains some sub-keys, which are nothing but the list of User Account Security Identifiers (SID). Each of the SID represents an Account. The key is located here:</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">HKEY_LOCAL_MACHINE \ SOFTWARE\ Microsoft\ Windows NT \ CurrentVersion \ ProfileList</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Identify the SID for your User account, and change the Profile path</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">To know the SID for your user account, you may use the script sidlist.vbs </span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Download the script and run it. (The User Account names and SIDs will be listed in a log file, and opened automatically.) </span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Note down the SID for your account. </span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Then, in the Registry Editor, select the correct SID that belongs to your user account. </span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">In the right-pane, double-click the ProfileImagePath value and change the profile path. ( The ProfileImagePath stores the full path of the User account home folder. ) </span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Example:</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">%SystemDrive%\Documents and Settings\OldUsername</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">becomes the following:</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">%SystemDrive%\Documents and Settings\NewUsername</span><br /></div><div style="font-family: inherit;"><span style="font-size: small;"><br /></span><br /></div><div style="font-family: inherit;"><span style="font-size: small;">Close Registry Editor, and restart Windows. See if you're able to logon to that user profile successfully. Additionally, to verify if the path has been changed successfully, type SET in the Command Prompt. In case you find any abnormal behavior when running an application, you may undo the above procedure.</span><br /></div>Unknownnoreply@blogger.com0