How to launch control panel items or objects from a RUN or CMD line.

Sometimes it is just simpler to run from CMD line control panel objects. It is even easier to get a user who does not have the menu items available to hand them a “RUN” CMD to open the correct control panel object you need them to. Below is a list of all the control panel objects just type the CMD in the RUN or DOS windows and you place a user right where you need them.

Accessibility Options
 access.cpl

Add/Remove Programs
 appwiz.cpl

Add Hardware Wizard
 hdwwiz.cpl

Automatic Updates
 wuaucpl.cpl
 
Bluetooth Properties
 bthprops.cpl
 
Display Properties
 desk.cpl
 
Firewall Properties
 firewall.cpl
 
Game Controllers
 joy.cpl
 
Internet Options
 inetcpl.cpl

iSCSI Initiator
 iscsicpl.cpl
 
Java Control Panel
 jpicpl32.cpl
  
Licensing Mode
 liccpa.cpl
 
Mouse Properties
 main.cpl
 
Network Connections
 ncpa.cpl

Network Setup Wizard
 netsetup.cpl
 
ODBC Properties
 odbccp32.cpl
 
Power Options
 powercfg.cpl
 
Regional and Language Options
 intl.cpl
 
Sound and Audio Devices
 mmsys.cpl

Stored Passwords
 keymgr.cpl

System Properties
 sysdm.cpl
 
Telephone and Modem Properties
 telephon.cpl

Time and Date Settings
 timedate.cpl
 
User Accounts
nusrmgr.cpl
 
Windows Security Center
 wscui.cpl

Wireless Link
 irprops.cpl

 

This works on Windows XP, Windows Vista, Windows 7, Windows server 2003 a/ R2 and Windows Server 2008 / R2

Repair and Reset TCP/IP Winsock Catalog Corruption in Windows Vista or Windows 7

Winsock 2 accommodates layered protocols. A layered protocol is one that implements only higher level communications functions, while relying on an underlying transport stack for the actual exchange of data with a remote endpoint. LSP  aka Layered Service Provider can be a security layer that adds protocol to the connection establishment process. An example of an LSP is the Microsoft Firewall Client Service Provider installed as part of the Internet Secutity and Authentication Server (ISA) on clients. The Microsoft Firewall Client Service Provider installs over the Winsock base providers for TCP and UDP.

To check which LSPs installed on your Windows Vista or Windows 7, use netsh winsock show catalog command.

Sometimes the winsock settings in Windows may get corrupted, causing errors and problems with Internet connectivity. When Winsock corrupts, the networking errors that you may face include unable to access network services, web pages, Windows update services or other odd network behaviors.

Now to reset Winsock we can use a similar cmd “netsh winsock reset”. 
What netsh winsock reset command does is it resets Winsock Catalog to a clean state or default configuration. It will remove anyWinsock LSP (Layered Service Providers) previously installed, including any potentially malfunctioning LSP that may cause the loss of network packets or transmission failures. So any previously installed LSPmust be reinstalled. This command does not affect Winsock Name Space Providers.

To repair and reset the Windows Vista or Windows 7

  1. Click on Start button.
  2. Type Cmd in the Start Search text box.
  3. Press Ctrl-Shift-Enter keyboard shortcut to run Command Prompt as Administrator. Allow elevation request.
  4. Type netsh winsock reset in the Command Prompt shell, and then press the Enter key.
  5. Restart the computer.

Good luck,

Cubert

The User Profile Service Service failed the logon. User profile cannot be loaded, when logging on to Windows 7 or Windows Vista

Ever get this when logging in to a Vista or Windows 7 system?  I seem to get it all the time, here is how to quickly fix it. By the way that is not a typo in my subjectline but how the error shows up when you try logging in. Not sure why but I am guessing that “User Profile Service is a Service and thus the “User Profile Service Service”  as the title of this post.

Log in with a admin account and run regedit. Go to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

You will find a key or maybe several keys that have “.bak” extenion on them. You will also find the same key with out the “.bak“, Rename the key without  the  “.bak”  to same name + “.new” then rename the Key with “.bak” removing the “.bak“.  Basically we are making the .bak key the original key and so forth.


Now that you have that done we need to edit 2 keys inside of the newly renamed key.  Choose the folder without .bak, in the right pane, double click RefCount and type 0 and then click OK, next choose the folder without .bak, in the right pane, double click State and type 0 and then click OK.

Close the regedit and logout and back in as the user profile that was failing. It should allow you in now.

I hope this helps someone out there

Cubert

Weird Network Issues, Can’t surf the web or web applications are failing but ping and DNS works?

There are many symptoms that may arise when you are installing a new firewall on a network that is using a DSL circuit and the MTU is not set correctly. That’s right the MTU, Max transmission Unit as it is know is a happy 1500 bytes on any Ethernet,  that medium makes up most endpoint networks on the Internet. Most admins never think about what the MTU is set at the gateway device, when they forget to realize that the circuit to the Internet is a DSL circuit they may see things on the network that can’t seem to explain.

MTU is the maximum packet size (in bytes) that can be transported reliably across any particular network; IP Ethernet in this case. The maximum size of an IP Ethernet packet is 1500, but overhead like IP, TCP, and PPPoE must also be taken into account. The wrong MTU will actually prevent you from accessing some web sites or FTP sites. It may even cause you to not authenticate properly on mail servers or secure web sites. There are too many variables to be able to estimate what your optimum MTU should be but my rule of thumb is -32bytes which makes the MTU 1468.

If your running a VPN to a remote domain and you are having domain failures that don’t seem to make since? Some people have no issues and others fail with different errors when the should work?

Only some websites working correctly?

DNS and ping work but other services  may fail like mail or ftp?

What maybe taking place is a conflict in the MTU available on a DSL circuit. The Ethernet is placing packets on the wire at up to 1500 bytes each but the DSL has only 14XX bytes available to it so a fragment has to take place that ends up breaking the request being made.

It is simple to overcome such a issue by setting the MTU of your firewalls DSL facing Ethernet device. This will then cause the firewall to regulate the MTU and control the MTU going out to the DSL circuit.

You can also change the MTU in a Windows workstation so it will not send out a packet bigger than what the DSL circuit can handle.

To do this edit the registry with REGEDIT and change the following key.

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\
Interfaces\[Adapter ID]]

Value Name: MTU
Data Type: REG_DWORD (DWORD Value)
Value Data: Default = 0xffffffff (1500)

This will fix the Windows system but I prefer to do it at the firewall so one edit changes all systems. Do what you need to do.

Hope this helps someone out there

 

Cubert

Monitor a WD ShareSpace using XYMon on any remote network

Do you happen to be a systems support guy who needs a method of getting the basic stats of a WD ShareSpace into your XYmon or MAG monitor? If you are like me then you are a systems admin responsible for many different networks spread across the Internet. You then may have deployed a few NAS systems including the WD ShareSpace that runs a version of BusyBox Linux. This is good news because WD provides access to the shell over SSH if you enable it via the web admin (advanced section). So now go enable SSH access and then puttythe system using the username “root” and a password of “welc0me”  where the 0 in welc0me is a zero.

With shell access we can do many things, one of which is getting the stats from the system.  Currently we have only 1 method to get the stats to XYmon but we are exploring some custom XYmon client binaries we can distribute in future versions of this article.  That may make this article a mute point so check back every so often for updates.

Today we have to do monitoring in 2 parts,

#1 Have a script on WD ShareSpace running on a regular intervals, that executes  the basic commands to produce the files we need to stat the system in XYmon.

#2 Have a Windows system grab the stat files from WD ShareSpace and process them before sending them on to the XYMon server.

First script is the WD Sharespace script which is a very simple shell script that does nothing more then cat to several text files ( meminfo, df, du, uptime and load) and saves them to a share on the WD ShareSpace called Public. You can modify the script to place files on any share you want. The script should then be executed with the following command while SSHed in to the WD ShareSpace

The first time you run the script you will need to make it executible. To do so type:

chmod 0755 ./Report.sh

The to run the shell script type:

Report.sh &

This will place the script in the background as a process and release your shell so you can logout without stopping the script. The script will run then sleep for 5 minutes then run again replacing files with updated files every 5 minutes until you stop it(which should be never).  You will need to change the permissions on the files the first time you run script so that the report files are world readable. To do this use the following command.

chmod 0777 ./*report.txt

We now have stat files on a share that we want to “FTP” off. The key word here is FTP so we will want to allow anonymous FTP to the WD ShareSpace. Login to the web admin of the WD ShareSpace and enable FTP on the device. This allows the Perl script we use next to grab the stat files, process them and then send them on to the XYmon sever via a proxy connection.

WDShareSpace Scripts

The next step is to setup the Windows system to proxy the stats to the remote XYMon server. I normally use one of the Windows server we monitor via XYMon but if this is the only thing you monitor then a windows desktop can be used as well. Either way you will need a Active State Perl set up on a Windows box to be the proxy.

Today the script is Perl, tomorrow it could be a Powershell or some other language suitable for Windows but for today it’s Perl. Perl is not native to Windows so you will need to add it’s language to Windows by the way of Active State Perl for Windows. To install ASP go to Active State Perl.  Install Perl and make sure you select to place Perl in the PATH variables with in Windows during install process. Now download our Perl script and place it in  a directory on your Windows server.

You should edit the script variables so that it reflects your setups, (Share to look for files in, the name of the WDShareSpace as seen on XYMon server ).  The run the Windows Scheduler and create a new daily schedule to run the perl script “WdShareSpace.pl”. After creating the daily schedule go back in and edit the schedule and select the advanced section. Find the “run every” and set it to 5 minutes and the in the “run for” place in 24 for 24 hours a day. This will get the script running every 5 minutes which is the same schedule as the shell script running on the NAS so you will get updates every 5 minutes.

So to summarize:

We have 2 scripts (Report.sh and WDSharespace.pl) Report.sh runs on the NAS and after permissions are changed it is executed with the (&) symbol after it so it drops to the background and keeps running when you close the ssh window. This script creates a set of report text files in the same directory as the script. The WDShareSpace.pl runs on Windows with Active State Perl installed and it has several varibles in script that need to be edited to point it to the NAS and XYMon servers and it is scheduled to run inside of Windows Scheduler(AT) on a 5 minute interval.

If all is successful you should get some thing like the following in your XYmon server if you configured the BBHOST for the WDShareSpace HOST.

Disk view:

How-to Setup Windows 2008 R2 Server Core As An Active Directory Server

Setup Active Directory on a Windows Server 2008 core

 

This is pretty simple actually; Install Windows as normal but selecting a Server Core as your installation medium. It will install just like a normal Windows 2008 install until the reboot process when it loads Windows for the first time. At the point it will ask for you to set your admin password and then boot to a Window’ish

Setup Active Directory on a Windows Server 2008 core

 

This is pretty simple actually; Install Windows as normal but selecting a Server Core as your installation medium. It will install just like a normal Windows 2008 install until the reboot process when it loads Windows for the first time. At the point it will ask for you to set your admin password and then boot to a Window’ish desktop where only a Command shell is available.

At first log in there are several things we need to do to prepare the system.

 

We need to assign the server a hostname

netdom renamecomputer %computername% /newname:YourServerName

Then we add our network information

netsh interface ipv4 set address name="Local Area Connection" source=static address=192.168.1.10 mask=255.255.255.0 gateway=192.168.1.1

Then we add our DNS servers

This should be the DNS address of your Active Directory DNS Server so replace 4.2.2.2 with that IP address.
netsh interface ipv4 set dns name="Local Area Connection" source=static address=4.2.2.2 primary

Confirm your new IP setup information

ipconfig /all

Now lets restart the system

shutdown -r -t 0

After we log back in from our reboot we join the existing domain

netdom join %computername% /domain:YourDomainName.

You notice I have a “.” at the end of the line! the denotes the end of the domain name and should be used.

Lets restart the server and bring it up as a member of the domain

shutdown -r -t 0

We should go ahead and activate Windows 2008 R2 now.

 cscript C:\windows\system32\slmgr.vbs -ato

Now we need to add the DNS-Server-Core-Role

ocsetup DNS-Server-Core-Role
 

To check if it was really installed we can run.

oclist |more

Now we dcpromo the server in the unattended mode

dcpromo /unattend /replicaOrNewDomain:replica /replicaDomainDNSNAME:YourDomainName  /ConfirmGC:Yes /UserName:YourDomainName\Administrator /Password:* /safeModeAdminPassword:YourPasswordHere

The (/Password:*) tells the Server to ask you it during the request to add after you run the command. The (/safeModeAdminPassword) sets what you want the local admin password to be if you need to log in “off” the domain.

The AD DS role will be installed and afterwords the server will reboot as a domain controller.

 

Now to make your job easier lets turn on Remote Desktop so you can RDP to the Windows 2008 Server Core and operate the command shell from remote.

cscript c:\windows\system32\scregedit.wsf /AR 0

I hope this helps someone out there get a Windows 2008 Server Core up and running as a Active Directory Server quickly.

Cubert

😎

\NETLOGON fnum 0x8007 returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED

Samba and Winbind Fix for Windows 2008 R2 Active Directory Services

Having issues with file sharing when inside a Windows 2008 R2 Domain? Are you getting these errors in you logs?
rpc_client/cli_pipe.c:rpc_api_pipe(790)
rpc_api_pipe: Remote machine 0.0.0.0 pipe \NETLOGON fnum 0x8007 returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED
A little searching online shows a lot of people with this or related problems, It looks like there’s a bug in the samba package that prevents

Samba and Winbind Fix for Windows 2008 R2 Active Directory Services

Having issues with file sharing when inside a Windows 2008 R2 Domain? Are you getting these errors in you logs?

rpc_client/cli_pipe.c:rpc_api_pipe(790)
rpc_api_pipe: Remote machine 0.0.0.0 pipe \NETLOGON fnum 0x8007 returned critical error. Error was NT_STATUS_PIPE_DISCONNECTED

A little searching online shows a lot of people with this or related problems, It looks like there’s a bug in the samba package that prevents it from working with Windows Server 2008 R2 domains. If you’re running into this problem, the solution is to remove your existing samba installation and install, instead, the samba3x packages.

Run the following on your Redhat or CentOS installation.

yum erase samba samba-common
yum install samba3x samba3x-client

You will need to rebuild your connections to AD via winbind and rebuild your SMB.conf so I would suggest you save your files before starting the process.

If you need help rebuilding Winbind and Samba this web post is a great example how to do it.

http://www.sweetnam.eu/index.php/Using_Active_Directory_for_CentOS

Enjoy.

P.s

When joining server to AD (step #9) in web post

 net ads join -U administrator@SWEETNAM.EU

It seems to join correctly if you just use “admin username” with out the @domain added to the line. It always seems to fail if I use the entire domain name in the join request. Instead I use the following example and it works great for me.

net ads join -U administrator

Good Luck

Cubert

Outlook Express “Compact Messages” pop-up

I have a user who every time they log in they get a pop up notice that Outlook Express needs to be compacted. They don’t use Outlook Express so why would it need to be compacted?

The short answer is that it does not. There is a issues with Windows Search indexing.

So here is the fix!

If you’re using Windows Search, right click the System Tray

I have a user who every time they log in they get a pop up notice that Outlook Express needs to be compacted. They don’t use Outlook Express so why would it need to be compacted?

The short answer is that it does not. There is a issues with Windows Search indexing.

So here is the fix!

If you’re using Windows Search, right click the System Tray icon, select Windows Search Options.  When the Indexing Options dialog box appears, click the Modify button at the bottom.  Find Microsoft Outlook Express in the list, clear the check box, click OK.  Microsoft Outlook Express should no longer appear in the “Index these locations:” list.  Close the dialog box.

After changing Windows Search Options, you may still have to reset the OE count.

Edit the registry manually to reset the counter manually:

1. Close Outlook Express and all message windows.
2. Click Start, click Run and type without quotes “regedit”.
3. Navigate to this key

HKEY_CURRENT_USER\Identities\{GUID}\Software\Microsoft\Outlook Express\5.0

where GUID is the long number used for your Identity.
4. In the right-hand pane, double-click “Compact Check Count”, then change the value to zero.
5. Close regedit and restart your computer.

Enjoy!!

Mac OSX Leopard Guest Setup under VirtualBox

MAC on Windows

How to install and run a MAC on a windows or Linux systems virtually has been made easy with the tools and instructions available for download. 

Download EmpireEFI and Full Pdf Manual here –>  MAC-Leopard_Vbox-VM

With just a little effort you can run MAC OSX 10 Snow Leopard on your windows system or linux system. You can buy OSX at BestBuy for about $30 and get for free

MAC on Windows

How to install and run a MAC on a windows or Linux systems virtually has been made easy with the tools and instructions available for download. 

Download EmpireEFI and Full Pdf Manual here –>  MAC-Leopard_Vbox-VM

With just a little effort you can run MAC OSX 10 Snow Leopard on your windows system or linux system. You can buy OSX at BestBuy for about $30 and get for free Vbox from the Web here at http://www.virtualbox.org/  . Then download the zip package above which includes the EmpireEFI ISO and the complete instructions on how to install into a VM using Vbox.

FYI

Intel hardware works better than AMD

Enjoy

Cleaning Up the Exchange 2003 Server’s SMTP Queues after NDR attacks

Warning: This process will delete all email that is due to go to external recipients. Internal messages are not affected, neither are new inbound messages from the Internet unless they are from the spammer continuing to try and abuse your server.

Capturing the Messages Into a Single Queue

This process requires an SMTP connector for all addresses. If you don’t already have one (with a * on the

Warning: This process will delete all email that is due to go to external recipients. Internal messages are not affected, neither are new inbound messages from the Internet unless they are from the spammer continuing to try and abuse your server.

Capturing the Messages Into a Single Queue

This process requires an SMTP connector for all addresses. If you don’t already have one (with a * on the namespace tab) then you need to create one using the instructions below. 
If you already have an SMTP Connector with a * on the namespace tab, then you can use it for this process. You will need to adjust the settings as appropriate. You may wish to just make a note of the settings, delete the connector and create a new one for this process. When complete recreate your live connector.

  1. In ESM, Connectors.
  2. Find default SMTP connector, select properties and then select “Address Space” Edit the SMTP entry and make it a cost of 2.
  3. Right click on connectors and choose New, SMTP Connector.
  4. On the “General Tab” type a name for the connector. “Spam Cleanup” or similar.
  5. Click the “Add” button under “Local Bridgeheads” and choose your Exchange server.
  6. Click on the “Address Space” tab.
  7. Click “Add” and choose SMTP. Leave each setting (* and cost of 1) and press ok.
    If all the spam is to one domain, then you could remove the * and enter the domain that the messages are being sent to. This should leave legitimate messages in the queue.
  8. Click on the General tab again. Change the option in the centre from DNS to “Forward all mail through this connector to the following smart hosts”.
  9. Enter an invalid IP address in square brackets:  [99.99.99.99].
  10. Click on the “Delivery Options” tab and ensure that “Specify when messages are sent through this connector” is selected.
  11. Change the option to 11pm. (If it is close to 11pm when you are doing this, use a much earlier time – 6am or similar. The time doesn’t matter as long as it is not close).
  12. Press Apply/OK to close the SMTP Connector dialogue.
  13. Restart SMTP Virtual Server.
    1. Expand Servers, <your server>, Protocols, SMTP.
    2. Right click on the “Default SMTP Virtual Server”
    3. Choose “Stop”. This may take a few minutes.
    4. Once it has stopped, right click again and choose “Start”.

The Exchange SMTP virtual server is now processing all the messages and placing them in to a single queue for your SMTP connector. This can take some time. You may want to wait until the number of messages in the queue stays constant before attempting the next stage.

Exchange 2000: The queues can be found in Servers, <your server>, Protocols, SMTP.

Exchange 2003: The queues can be found in Servers, <your server>, Queues.

Deleting the Messages

Now that the messages are in one queue, it is quite easy to delete them

Exchange 2003

  1. Right click on this connector and choose “Find Messages”.
  2. In the drop down box select the number of messages to be listed in the search.
  3. Click “Find Now”.
  4. Once the search is complete, select all of the messages (use the shift-page down key combination)
  5. Then click “Delete all Messages (No NDR).

Exchange 2000

  1. Right click on this connector and choose “Delete All Message (No NDR)”
  2. Select Yes when asked if you want to delete all the messages in the queue.

Once the messages have been deleted, which could take some time, refresh the queues to ensure that they don’t continue to build. If they do then Exchange is still processing the messages. You will need to repeat the procedure to delete more messages until the queues are completely clear and stay at zero.

Once you have flushed out the messages, undo the changes that you have made.

If it was a new SMTP connector, delete it.
If you adjusted an existing connector, put the settings back how they were. Don’t forget the time on the “Delivery Options” tab. it should be “Always Run”.

Finally restart SMTP virtual server to get Exchange to start using the new settings.