Comments for BFTech Impressions

Comment on Replacing the Hard Disks in an Iomega StorCenter ix2 by Rui

Rui — Mon, 01 Mar 2010 11:33:08 +0000

Hi!
Does any one have the image of the system linux files for the ix2?
Both of my HDD have broken down! Now i’m missing the system!
Please help me !

send me a message to

metemedo24(at)gmail.com

Thanks,
Rui

Comment on SBS2008 Migration: Active Directory replication is taking longer than expected. by Karl Gesslein

Karl Gesslein — Sun, 28 Feb 2010 18:11:47 +0000

Thanks that helped me out a lot. I had to do the registry hack with SP1 as well because it wouldn’t let me past it. I was so frusterated I was about to reboot the SBS2008 server, glad I didn’t. Thanks again.

Did the hotfix and didn’t reboot the SBS2003 server and it kept going. What a hassle.

Karl

Comment on Updated: Configure PPTP on a Watchguard Firebox Using RADIUS Authentication and Windows 2008 by Tedfrd

Tedfrd — Sun, 28 Feb 2010 01:34:35 +0000

Great Article, but needs an additional step to work.
I’m running a Firebox x750e running Fireware 11.2 and Server 2008.

You need to configure a “Connection Request Policy” as well.

After you have completed step 5 above, then follow this set:

1) Right click on Connection Request Policy and Select “New”
2) Type in a corresponding name for the Policy, leave the Access Server as “Unspecified” and click Next.
3) ADD a condition and scroll down to the RADIUS Client and double click “Client Friendly Name”. Type in the name you used for your firebox, (Firebox). Case Matters here. Click OK - Next.
4) Accept the Defaults and click NEXT.
5) Leave the Authentication Methods unchecked and click NEXT.
6) Accept the Defaults for Configure Settings and click NEXT.
7) Click FINISH to complete the wizard.

Now do step 6 and configure the Authentication Policy.

Have found you need this “Connector” to make the entire PPTP-VPN connections.

Comment on SBS2008 Migration: Active Directory replication is taking longer than expected. by Mike

Mike — Sat, 27 Feb 2010 12:56:45 +0000

Had the same issue with active directory replication taking longer than expected. LDAP bind ok but would keep saying it was trying to finish replication.

To cut a long story short this is what I had to do:

Aborted migration, restored sbs2003 box from backup and started again.

File replication service on sbs 2003 box had been set to manual: Set to automatic and started service. This created a journal wrap error condition because FRS had been disabled for so long. Implemented registry fix as specified in the event log.

Also installed MS hotfix with regards to problem being caused by previous authoritive restore. I have no idea if one had been done in the past but as MS say that it will stop the condition from occuring as well as fix the issue I thought better safe than sorry.

Restarted migration and locked up at same location but this time GP couldn’t be processed because of authentication issus (LDAP bind failed). I found a comment above where someone changed the DNS address on the sbs2008 box and thought I’d give it a try.

According to the network settings on the SBS2008 box the primary dns was the sbs2003 server and the secondary was the sbs 2008, I swapped these around making the SBS2008 box the primary for itself and hey presto off we go.

Please note though the progress bar didn’t just start moving immediatley afetr making this change, it actually took a good 10mins or more but if you watch the system event logs you should see an entry stating that Group Policy was successful and then a whole bunch of events will follow as things start to progress, so have a little patience after making these changes.

Comment on SBS2008 Migration: Active Directory replication is taking longer than expected. by Riddhim Dhawan

Riddhim Dhawan — Wed, 24 Feb 2010 13:37:55 +0000

I had exactly similar issues. The logs looked the same. You will notice that when you check the operation masters on 2003 SBS server they will show and ERROR on operation master and in AD sites and services the replication link will be missing on the 2008 server.
Out of frustration I rebooted the 2008 server during the setup and hell crashed on me. The source server was in the middle of migration and schema had been changed to a no comming back stage. I did a restore on the source server once when it crashed and started setup again with image on the source server.
I tried to do the install manaully without the answerfile but the same issue. The server is happy until I promote it to a Domain Controller. Then I get the following error message regarding Group Policy:
“The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function call failed). Look in the details tab for error code and description.”

I started the setup again and got stuck at excatly the same spot. I pressed ctrl+alt+del on 2008 and started eventvwr from task manager. It showed the following errors.
Source; GroupPolicy
Event ID: 1006
The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller (LDAP Bind function call failed).

I then installed the hotfix from MS as mentioned in the article and everything was fine.
Thanks guys.

This is what I have learnt.
1. Check clocks are in sync.
2. Check FRS, DNS and DHCP on Source Server ( Some idiot had DNS set it to manual on my server).
3. I was prompted for 2003 SP1 not installed where as I had SP2 on it. ( I added the reg key manually on the 2003 ! Setup is dumb.
HKLM\SOFTWARE\Microsoft\SmallBusinessServer\ServicePackNumber ( = 1) )
4. Check Sysvol permissions.
5. Install the hotfix FIX 226580
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=939820&kbln=en-us
6. Always take an image backup of source before you start anything. There are things that can go terribly wrong as they went worng with me.

Cheers
Riddhim