Wednesday, July 29, 2015

Dell Poweredge 1950 Import Foreign Configuration Strike F1

This could mean a few things, a drive has failed and you inserted a new drive, hopefully it was a raid other than 0 right? Or it could also be that an issue happened on a reboot and all you need to do is import the foreign configuration.

During POST Boot to the CTRL-R utility, make sure you are on the  VD Mgmt screen, highlight controller at the top-left, hit F2,  select Foreign, then select Import.

Now, if you are just wanting change drive to install a new OS for testing purposes, it is the same process, but you will need to initialize the NEW drives and create a new raid set. Do NOT, I repeat do NOT initialize the source main drives when switching back or you will lose everything. Also check the boot order of drive sequence in bios after changing back to the original drives. I was getting the F1 to reboot because something else was the 1st selection and for some reason, the system did not try to go to the second (PERC controller) for boot.


Sunday, December 28, 2014

Office 2010 Error 1935

Wow! This error was a persistent error. Tried so many things to fix this. Uninstalled .net, ran a uninstall cleaner, ran a registry cleaner(three different ones) and nothing worked! I finally came across a very helpful post, Google searched Office 2010 Error 1935. Second Page (I know right, you got to be desperate to go to the second results page) and BAM! there was the EASIEST fix I have done, and this one worked for me!

*Disclaimer, this post is without warranty, etc. etc. I am not responsible for your computer crashing, or you losing all your pictures and documents, try this at your own risk.*

Step 1: Windows+R>regedit then hit enter

Step 2: Locate HKCU\Software\Microsoft

Step 3: Locate Key/s named Office and/or OfficeSoftwareProtectionPlatform (only Office was listed for me)

Step 4: Delete key/s, then reboot, install office and profit!

Again, this was my experience and this worked for me. Mileage may vary. Good luck, and happy troubleshooting!

Big thanks to Sammit over at http://sammit.net/how-to-fix-error-1935-when-installing-microsoft-office-2007-or-2010/ for posting this easy solution and saving the day!


-Oscar


Update 1: I had to disabled Ad Aware Anti-Virus as it was causing issue with installing certain programs. Ended up removing it all together and going a different route. Make sure you disable antivirus as well to see if that is the issue.

Friday, December 26, 2014

DCPROMO fails with: 'Failed to configure the service NETLOGON as requested' Server 2003

We have been working with a client on getting rid of the 2003 domain controllers. Came across one domain controller that wouldn't demote. Ran dcpromo and got this:

The operation failed because:

Failed to configure the service NETLOGON as requested


The reason for my clients failure was because the primary DNS server was the server itself. So DC1 with an IP of 10.0.0.0, had the first DNS entry as 10.0.0.0.

After I changed it to the new DNS server IP, I ran dcpromo again and it worked like a charm, no reboot needed. I did do a ipconfig /flushdns, just because though. Also, according to Microsoft you should not have a domain/DNS server pointing to itself as the first entry. The first DNS entry should be another DNS server, and use the local host address of 127.0.0.1 as the second entry. I won't go into detail as why, but a quick search should give you all you need. Enjoy!

Wednesday, October 1, 2014

How to: Server 2008R2 RDS Re-Arm for another 120 days.

You know, sometimes you just couldn't get that budget request in to get those RDS licenses ordered and installed. It happens, especially is this day in age. I searched everywhere on how to re-arm the trail for RDS, to no avail! All the answers I saw were, rebuild the server or buy the licenses. Sure, let me just rebuild a server just because (if that is an option, more power to you). Here is a simple way to re-arm the trail for RDS.

Locate in the registry editor and find this folder:
HKLM\SYS\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod



Just delete the key inside this folder, reboot and you will have another 120 days to work with. Enjoy!



Friday, February 28, 2014

Xerox ColorQube/WorkCentre x86 driver on x64 Print Server

Hello everybody!

I am going to explain how to install a x86 Xerox driver on a x64 Print server.

Make sure you go to the Xerox driver page and download both the PS driver for x86 and x64. Install the x64 driver as usual with the print manager.

Now, for the x86 driver, it will ask for a i386 folder/destination. Here is where I got into trouble.

Called Xerox Support and they stated to download the GLOBAL 32 bit PS driver. For some reason, the Microsoft certified driver file does not contain the ntprint file that it needs to install the x86 driver.

As soon as I downloaded that Global print driver, I went through the install process again, this time when it asked for the i386, I pointed it to the global print driver folder and it found the ntprint file it needed. BAM, worked like a charm. Now my 9203 ColorQube is installed on my 2008R2 print server with both x86 and x64 drivers. Sweet.



Big thanks to Xerox for the quick call back and assistance.

Wednesday, July 25, 2012

Break Key for HP DV6 Laptop!

So I am at home working on an old router I was allowed to take from work. Well this router has a password no on knows, so I need to fix that :). Anyways, everyone who works on routers knows to interrupt the boot up process you need to hit the break key. Well guess what, the HP DV6 laptop doesn't have a freaking BREAK key.

I searched forums and google for 20 minutes nothing! I was just looking around in my accessories > ease of access(win 7) and came across my on screen keyboard. Well guess what, the on screen keyboard has a ScrLK key, which my damn laptop doesn't have.

I powered down the router, powered up the router held ctrl on my physical keyboard and hit ScrLk with the mouse...BAM right into rommon 1> mode! Woot, now to reset this start up config and do whatever I feel like! :)

Wednesday, November 30, 2011

Open NAT PS3 MW3/Actiontec Q1000

REJOICE, THE HOUR IS AT HAND, the hour of having an open NAT that is!

After countless hours configuring my Q1000 modem/router, I have finally obtained an open NAT on my PS3. The process is quit simple, and I honestly just missed one little step, and that step would have saved me hours upon hours of trying to get an open NAT.

First off, I want everyone to know that I have all three consoles (I mean who doesn't, and if you don't why not?). I want to bring to light that, I had an open NAT on my Xbox, but always had a moderate NAT on the PS3. Well, I had black ops for both systems, but I only have MW3 for the PS3 so that is the system I wanted my open NAT on.

I will start off by saying it is very difficult to have an open NAT for two systems connected to the same router. Actually I want to go ahead and just say its not possible, and here is why. 98.9% of home users have cable/dsl and with that, only one public IP address. This isn't something to be worried about, that is just how it goes. Well with one public IP address, you can only have one system with an open NAT. You could call your ISP and get two IP addresses, but that costs some cash and if you're like me, you are not willing to dish out even one more cent to the man! So therefore, you are stuck with your single public IP address, and two systems (I do have all three, but I don't play multiplayer on the Wii, so that isn't an issue). Ok, enough of this rambling and background blah blah, on to the fun stuff!

*Disclaimer, only perform the below listed steps if you are the owner of the router, or get permission from the owner (this applies to all you youngsters still living with the parents). I am not responsible for any issues your router may have by performing the steps I will list below, nor will I buy you a new router if you break it (which is highly doubtful but hey, I work in the IT field, I have seen stranger stuff happen).*

I want to say that, what I will discuss will be with the assumption that you have some IT knowledge. I am not talking about building Virtual Servers from ground up or deploying a bran new Domain controller on a network with 300+ employees (which I can do, allllll yeahhhhh). But enough knowledge to know how to access your router.

Unless you changed something, then your router IP will probably be 192.168.1.1 or 192.168.0.1. Type this address (or your address) into your web browser URL and hit enter. If neither of these address work, on your home computer go to Start>Run (XP) Search(Vista and up)>'type' cmd>'type' ipconfig in the cmd window. You're looking for Default Gateway, that address should get you into your router.

Be sure to enable a static IP address for the PS3, if you do not know out to do this, do a Google search and get it done before reading on.


This will bring you to the router configuration page/s. Look for UPnP configuration page, and ensure that this is enabled. Before reading the below steps, look for DMZ configuation page. Remember that static IP you just gave to your PS3, well enter here and enable DMZ mode. What this will do, is place the PS3 outside of the router and use the public IP address directly. Load up MW3 and look at your NAT, if this does not work, remove the PS3 from the DMZ (this is important) and disable the DMZ and read on.

If the DMZ option failed, what we are looking for is port forwarding now. Find and enter onto the port forwarding page. Here are the ports you will want to forward for MW3:

"...
  • Set port forwarding on your router to the IP address of your PlayStation 3. This game uses ports 81, 3074, 3075, 3478, 3479
    (UDP) and ports 80, 443, 3074, 5223 (TCP).
  • For voice / video chat and online game play, direct communication with other PS3™ systems is used for data transmission during voice / video chat and online gaming. The port number used for this is UDP: 3658
..."

Original source: http://activision.custhelp.com/cgi-bin/activision.cfg/php/enduser/std_adp.php?p_faqid=77659&p_created=1320244623&p_sid=G49GniIk&p_accessibility=0&p_redirect=&p_srch=1&p_lva=77658&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MSwxJnBfcHJvZHM9MCZwX2NhdHM9JnBfcHY9JnBfY3Y9JnBfc2VhcmNoX3R5cGU9YW5zd2Vycy5zZWFyY2hfbmwmcF9wYWdlPTEmcF9zZWFyY2hfdGV4dD03NzY1OQ!!&p_li=&p_topview=1

and here are the ports in general for the PS3 system:

TCP Ports: 80, 443, 465, 983, 5223, and 10070 - 10080 - UDP Ports: 3478, 3479, 3658, and 10070


Also remember that, when setting port forwarding, "for a single port Port Start, Port End, and Port Map are all the same number. For a range of ports, Port Start is the first port of the range. Port End is the last port of the range and Port Map is ALWAYS the same as Port Start (Source: Actiontec Tech support e-mail)."

So for example, if you have a range of ports, like 3074 and 3075, you would enter it like this

Port Start: 3074
Port End: 3075
Port Map: 3074

Single Port exmaple:

Port Start: 80
Port End: 80
Port Map: 80

Now that you have your port mappings, let me give you a little tip. You cannot have two ports open for two different systems. One will cancel the other out. If you have port 3074 mapped for your Xbox and PS3, which ever one is listed first, will take priority. This is what plagued my moderate NAT for the PS3, because my Xbox had 3074 mapped first. After removing the Xbox map, my PS3 had an open NAT and my Xbox has a moderate.

If you have any questions, please leave me a comment below and I will answer to the best of my ability, and if time permits I might even be able to offer assistance to you. Enjoy your open NAT on the PS3 system for MW3!!!!