a Flo + a Blog = a Flog my ブログ

12Dec/110

wbadmin to include all volumes

I am not sure why but I ended having to use wbadmin to do a full backup of a server. I usually do a -criticalonly to get a bare-bone restore of some windows 2008 r2 servers but I needed a include everything a specific server had.

I took me almost an hour to figure out how to use the -include parameter.

As from technet or the embedded help:

-include       Specifies the comma-delimited list of items to include in the
backup. You can include multiple volumes. Volume paths can be
specified using volume drive letters, volume mount points, or
GUID-based volume names. If you use a GUID-based volume
name, it should be terminated with a backslash (\). You can
use the wildcard character (*) in the file name when
specifying a path to a file. Should be used only when the
-backupTarget parameter is used.

This said if I listed the volumes separated by a comma it would not let me. So just to save time to someone trying to do something like: wbadmin start backup -backuptarget:\\somewhere\here -systemstate -vssfull -allcritical -quiet -include:a:,b:,c:,d:,e:[...] to put the list of volumes to include between double quotes. -include:"a:,b:,c:,d:,e:[...]"

I cannot believe that this is not mentioned anywhere.

Tagged as: , , No Comments
8Jun/110

Windows 2008 x Data Protector: Can not connect to the SCM (Service Control Manager)

I noticed this a while ago but a colleague came to me with this problem. Luckily - and because I have short memory, I documented the process accordingly - which he did not read... anyways.

With windows 2008R2, in order to deploy the client to the server - locally or remotely - one will need to make sure the account used to deploy the agent is in the inet password account list and part of the install server user list. If not it will need to be added as follow.

C:\Program Files\OmniBack\bin>omniinetpasswd -add youraccount@domain.net

C:\Program Files\OmniBack\bin>omniinetpasswd.exe -inst_srv_user youraccount@domain.net

Use -list to get a list of users already in the list. If you do not add your account, you will have to use the backup service account to deploy any clients.

Tagged as: , , , , , No Comments
15Apr/110

Robocopy and EMC Celerra

I came across a problem when using Robocopy command scripts when copying files from NTFS to EMC Celerra file system. The problem was that every time Robocopy was told to copy files to the EMC Celerra over the WAN, the files were always detected as “newer” on from the originating source. This caused Robocopy to copy every single file from our network to the remote network each and every time.

I came across a command line switch for Robocopy: /FFT : Assume FAT File Times (2-second date/time granularity).  The NTFS date and time stamp is a 64-bit variable, which DART doesn’t deal with.  So what this does is force Robocopy to use FAT style time stamps which are 2-second granularity. It allows enough flexibility to account for the way the time is recorded when doing a file copy from NTFS to another file system. This is needed when going between and NTFS and Linux/Unix/FAT or emulated file system.

update 20110601: I now use fastcopy instead of robocopy. It is a great fast(er) and friendly tool! And it doesn't have any of the security or date issues I have seem with the msft tool.

Filed under: En, IT, Windows, xNix No Comments
17Nov/100

Using 32-bit .Net Applications on a 64-bit system

I needed to use the Windows Mobile Security Power Toy the other day. So I download the power toy, fired it up, and watched it promptly crash. After several failed attempts I figured there was something wrong with my computer, so I went to another computer and did the same thing with success. In trying to diagnose the problem I went to another computer and tried to run the power toy and it crashed there also. So what was the problem?

In looking at the similarities and differences among the computers I realized that the two computers on which the application crashed had one thing in common - they were 64-bit machines whereas the machine on which the power toy worked was a 32-bit machine. I ran into a problem like this years ago. I had a .Net application that P/Invoked some 32-bit APIs. The computer would automatically load the .Net code in a 64-bit process, but 64-bit and 32-bit code cannot coexists in the same process which is why the program would crash. When I ran into this problem years ago I just changed the settings on my project so that the code would NGEN to 32-bit code (that means it was converted to x86 code at compile time). But I don't have the source code for the Windows Mobile Security Power Toy. So what could I do?

There's a command line utility that would help me here. It allows one to start a .Net executable and load it into a 32-bit process. the utility is named CORFLAGS.EXE. I went back to the 64-bit machines, opened the command prompt, and typed the following:

COREFLAGS.EXE SecurityManager.exe /32BIT+

Success!

Tagged as: , , No Comments
27Apr/100

Troubleshooting windows key management

I have recently been deploying a few windows 2008 R2 and I ran into some activation issues. Where the KMS could not be found and/or did not activate the servers.

First off, there a few commands and output that will give you a good starting point.

C:\Windows\system32>cscript slmgr.vbs /dlv
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Software licensing service version: 6.1.7600.16385

Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System - Windows Server(R), RETAIL channel
Activation ID: 039998e3-3ef5-4adf-b758-mnbvczxlkjjhh
Application ID: 55c92734-d682-4d71-983e-lkdaskdjaskl
Extended PID: 00477-4444-444-000000-00-1033-7600.0000-3482009
Installation ID: 006386735361234567898785803475982043689521915735258065
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: 2YYCD
License Status: Initial grace period
Time remaining: 43200 minute(s) (30 day(s))
Remaining Windows rearm count: 2
Trusted time: 4/27/2010 11:09:12 AM

Or its equivalent with less information slmgr /dli.

In that case, it seems that KMS client is not even set here.

First off, you may want to tell the server where to look to get Keys using the following commands.

To know which server should be register you may want to check the DNS record that

C:\Windows\system32>nslookup -type=srv _vlmcs._tcp.xxxx.net
Server:  rrrpdcad02.xxxx.net
Address:  10.9999.15

_vlmcs._tcp.xxxx.net   SRV service location:
priority       = 0
weight         = 0
port           = 8081
svr hostname   = rrrmskms01.xxxx.net
rrrpmskms01.xxxx.net   internet address = 10.99.98.97

With this information you can now register for this server.

C:\Windows\system32>cscript slmgr.vbs /skms rrrpmskms01:1688
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Key Management Service machine name set to rrrmskms01:1688 successfully.

You will then need to enter a valid key if not already done with you unattended install. Please check the below table with MS provided keys for activation using KMS.

C:\Windows\system32>cscript slmgr.vbs -ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Installed product key YC6KT-GKW9T-YTKYR-T4X34-R7VHC successfully.

then trying the activation using the command below I would get another error.

C:\Windows\system32>cscript slmgr.vbs /ato
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Activating Windows Server(R), ServerStandard edition (039998e3-3ef5-ddasdasdass8-d25fa0128ff4) ...
On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0x80072EE2' to display the error text.
Error: 0x80072EE2

Using the mentioned command I would find that 0x80072EE2 means that the operation timed out. Very well, then I may facing some communication errors.

Indeed, as you may have noticed I made a mistake above not using the right port. I used 1688 which the default port instead.

You can also check on your KMS for a status using the slmgr /dlv command:

Key Management Service is enabled on this machine
Current count: 50
Listening on Port: 8081
DNS publishing enabled
KMS priority: Normal

Be sure to use the port that is given by the volume license DNS entry and make sure it communicates. As you may have guessed there are 2 ways a new server where a KMS is install will register. Of course after changing to the right port and can try -ato (activation) again.

  1. by using the DNS to automatically locate the KMS
  2. or just register it manually using the commands above

When rightfully registered the /dli or /dlv will give you something like that:

C:\Windows\system32>cscript slmgr.vbs -dli
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT channel
Partial Product Key: R99HC
License Status: Licensed
Volume activation expiration: 259200 minute(s) (180 day(s))

Key Management Service client information
Client Machine ID (CMID): 70e4de42-rewa-4c93-gf45-a6d372bc0a19
Registered KMS machine name: rrrpmskms01.xxxx.net:8081
KMS machine extended PID: 55041-009999-313-09999-03-1033-6002.0000-3442009
Activation interval: 120 minutes
Renewal interval: 10080 minutes
KMS host caching is enabled

Activation Keys table (taken from here)

Operating System Edition Product Key
Windows 7
Windows 7 Professional FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
Windows 7 Professional N MRPKT-YTG23-K7D7T-X2JMM-QY7MG
Windows 7 Enterprise 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Windows 7 Enterprise N YDRBP-3D83W-TY26F-D46B2-XCKRJ
Windows 7 Enterprise E C29WB-22CC8-VJ326-GHFJW-H9DH4
Windows Server 2008 R2
Windows Server 2008 R2 HPC Edition FKJQ8-TMCVP-FRMR7-4WR42-3JCD7
Windows Server 2008 R2 Datacenter 74YFP-3QFB3-KQT8W-PMXWJ-7M648
Windows Server 2008 R2 Enterprise 489J6-VHDMP-X63PK-3K798-CPX3Y
Windows Server 2008 R2 for Itanium-Based Systems GT63C-RJFQ3-4GMB6-BRFB9-CB83V
Windows Server 2008 R2 Standard YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Windows Web Server 2008 R2 6TPJF-RBVHG-WBW2R-86QPH-6RTM4
Tagged as: , , , , No Comments
   Older Entries »

Twits

ING Direct Referal

Blogroll

Follow me

Jp

Kr

Languages

Sites of Mine