How to enable file content search in Windows Server 2008 R2

Import-Module ServerManager
Add-WindowsFeature FS-Search-Service
Posted in Uncategorized | Leave a comment

Change The default maximum size of XML WSUS Server

DONNERSTAG, 12. AUGUST 2010

ConfigMgr “Install Software Updates”

task failing when building a reference machine

error messages

One or more updates failed to install, hr=0x80004005

Failed to run the action: Install Software Updates.

Unspecified error (Error: 80004005; Source: Windows)

Unable to get locations, no need to continue with download

Failed to download update Error = 0x80040669

Solution 1

install the latest windows update agent before running the “install updates” task.

Solution 2

Add “SMSSLP=” into the sccm client installation properties in the task sequence, or add a registry value HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\SMSSLP and set it to .

Solution 3

The current number of roundtrips allowed by WSUS is 200 per client session.
The default maximum size of XML data that WSUS allows during each roundtrip is currently 200 KB.
To reduce the number of roundtrips to be within the 200 roundtrip limit per client session, you can adjust the adjust the maximum size of XML data downloads per trip from the 200 KB limit to an unlimited size.

To adjust the maximum size of XML allowed per request, you will need to adjust a setting within the WSUS SUSDB database.
You can adjust this setting by running the following SQL script on the WSUS server:

==========
USE SUSDB
GO
UPDATE tbConfigurationC SET MaxXMLPerRequest = 0
==========

NOTE: You will need to run this on the WSUS/SUP. You should check to see if the SUSDB is hosted by the default Windows Internal Database (WIDS) or by full SQL. You can check the following registry keys on the SUP to determine what is hosting SUSDB:
HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup\SqlServerName

Solution 4

If you are using protected distribution points, you will need to unprotect one of them to create your base image, also, in the advertisement for your task sequnce, ensure that the following options are enabled: “When no local distribution point is available, use a remote distribution point” (This one is especially required when using AD Sites as boundaries as there is no AD Site before joining the domain) and “When no protected distribution point is available, use an unprotected distribution point.”

Solution 5

Build and Capture task sequence is not a domain joined machine so it is unable to query for D site boundaries. Create a new IP Subnet Boundary and it should be working.

Solution 6

1. Check the “Allow HTTP communication for roaming and site assignment” site setting in the site mode tab of site properties. (On the site server you will be using for creation of the gold image)
2. Modify the “MobileClient.tcf” file (\bin\i386) to change the setting “IISSSLState” in the [Site] section to be 95 (IISSSLState=95) on the site server.
3. Re-create the bootable media (if you are using bootable media)

 Picture Window-Vorlage. Powered by Blogger.
Posted in Uncategorized | 1 Comment

Windows Server 2008 R2 (vmware VM) started hanging at applying computer settings forever

Solution:

Start Safe Mode with command prompt.
C:\Windows\System32>net stop “windows management instrumentation”
C:\Windows\System32>rename .\wbem\Repository .\wbem\Repository.Renamed

Posted in VMware, Windows | Leave a comment

Using KMS Manually to Activate Software

Using KMS Manually to Activate Software

This page is intended for technical support providers and network administrators. If you’re not one of those, you should talk to your TSP or net admin before proceeding. The concept behind the procedure on this page is explained on our main KMS page.

This page describes how to manually activate products. With this method, you’ll need to run commands on each machine – and for each software package – during the 30 day grace period after installation. If you are using virtual machines for testing and cross-compatibility on Macintosh computers, you’ll need to use the manual method in those circumstances.

KMS activation can be blocked by a firewall. Please be sure that any firewalls between the client machine and the KMS server are open to incoming and outgoing traffic on TCP port 1688.

To use this method, first install the software (Windows or Microsoft Office). As part of that process you’ll be informed that you have 30 days to activate the product. Complete the steps below during that 30-day period.

This method assumes that Windows or Office has never been activated on this machine before. If your machine had previously been activated with the earlier MAK activation method, please instead follow the instructions to switch from MAK to KMS activation.

 

Activate a Windows Operating System: Windows 7, Windows 8, Server 2008, Server 2008 R2, or Server 2012:

  1. Open up an Elevated Command Prompt window. For instructions, please see our guide: How To Open an Elevated Command Prompt.
  2. In the elevated Command Prompt window, verify that the current directory isC:\Windows\System32. If it is not, type
    CD \Windows\System32
    and press Enter.
  3. Type the following command:
    cscript slmgr.vbs /skms kms01.cit.cornell.edu
    and press Enter.
    (Note: The url in the command above begins with kay-emm-ess-zero-one.)
  4. Type the following command:
    cscript slmgr.vbs /ato
    and press Enter.
  5. Close the Command Prompt window.

And you’re done for that installation of Windows on that computer.

 

Activate Microsoft Office (2016, 2013, or 2010)

  1. Open an Elevated Command Prompt window. For instructions, please see our guide How To Open an Elevated Command Prompt.
  2. Type the following command, depending on your version of Office:
    • Office 2016:
    • CD \Program Files\Microsoft Office\Office16
    • Press Enter. This assumes you installed Office in the default location.
    • Note: If you installed the 32-bit version of Office on a 64-bit system, use this command instead:
    • CD \Program Files (x86)\Microsoft Office\Office16
    • Office 2013:
    • CD \Program Files\Microsoft Office\Office15
    • Press Enter. This assumes you installed Office in the default location.
    • Note: If you installed the 32-bit version of Office on a 64-bit system, use this command instead:
    • CD \Program Files (x86)\Microsoft Office\Office15
  • Office 2010:
    • CD \Program Files\Microsoft Office\Office14
    • Press Enter. This assumes you installed Office in the default location.
      • Note: If you installed the 32-bit version of Office on a 64-bit system, use this command instead:
      • CD \Program Files (x86)\Microsoft Office\Office14
  1. Type the following command:
    • cscript ospp.vbs /sethst:kms01.cit.cornell.edu
    • and press Enter.  (Note: The url in the command above begins with kay-emm-ess-zero-one.)
  2. Type the following command:
    • cscript ospp.vbs /act
    • and press Enter.
  3. Close the command prompt window.

And you’re done for that installation of Office on that computer.

 

Posted in Uncategorized | 1 Comment

IIS Admin service would not start with error -2146893809

IIS Admin service would not start with error -2146893809

by  on May.25, 2011, under IIS, Microsoft

In the event viewer you should see error with Event ID 7024.
The IIS Admin Service service terminated with service-specific error %%-2146893809.

Here is a possible fix. For the service to start it needs RSA MachineKey and access to it. The Key is stored in C:\Users\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys(for Server 2008)  you should see some files in that location with the size of 2 or 3 Kbytes. Look for the file name that starts with ‘C23’. This is the key that is used by Microsoft Internet Information Server. Check the permissions on that key and make sure that ‘System’ and‘Administrators’ have full control on this key. Once the permissions are set try starting IIS Admin service.

Posted in Windows | Comments Off on IIS Admin service would not start with error -2146893809

How to increase Windows 2008 R2 partition without shutdown

Open CMD and type

Diskpart

List volume

Select volume

extend

Posted in Windows | Leave a comment

FAS @ Microsoft


Posted in Uncategorized | Leave a comment

როგორ გავააქტიუროთ ვირტუალური RedHat ლინუქსი

download

როგორც ვიცით, შესაძლებელია RedHat-ის ლიცენზიის ყიდვა ვირტუალური გარემოსთვის და მისი ულიმიტოდ გამოყენება განუსაზღვრელი რაოდენობის ვირტუალური სერვერებისთვის. https://www.redhat.com/apps/store/server/rhel.html

მისი რეგისტრაციის პროცესი შემდეგნაირად ხდება.

პირველ რიგში DVD-დან უნდა დავაყენოთ პაკეტი virt-who

yum -y install virt-who

ამის შემდეგ ვახდენთ მის კონფიგურირებას

#subscription-manager identity

აქედან გავიგებთ ESX_OWNER-ს    

 #vi /etc/sysconfig/virt-who

 

VIRTWHO_ESX_OWNER=5847285
VIRTWHO_ESX_ENV=Library
VIRTWHO_ESX_SERVER=vcenter-server.example.com
VIRTWHO_ESX_USERNAME=administrator
VIRTWHO_ESX_PASSWORD=MyGNU4pass!!
VIRTWHO_DEBUG=1
VIRTWHO_ESX=1

რამდენიმე მომენტი რაც მანუალებში არ წერია.

თუ იუზერი არის დომენის და ვწერთ ასე domain\user  აუცილებლად დაწერეთ შემდეგნაირად domain\\user

 

და მეორე თუ პაროლში ურევია სპეციალური სიბმოლო(ები) პაროლი უნდა ჩასვათ ‘ ‘ -ში.

 

ამის შემდეგ ვსტარტავთ სერვისს:

# service virt-who start
# chkconfig virt-who on

და ბოლოს ვარეგისტრირებს სისტემას შემდეგი ბრძანებით:

 

# subscription-manager register –username user@redhat_portal –password password@redhat_portal –auto-attach

 

მარტივია, თუმცა კი შეიწირა ჩემი კვირა დილა სანამ გავიხსენე როგორ კეთდებოდა 🙂

 

P.S. თუ ყველაფერი ისე არ წავიდა როგორც ჩვენ გვინდა შეგვიძლია ლოგები ნვახოთ სადაც ზუსტად ეწერება რაშია საქმე.

tail -f /var/log/rhsm/rhsm.log

Posted in Linux | Leave a comment

როგორ დავაკონფიგურიროთ ერთზე მეტი IP მისამართი ერთ ქსელის კარტაზე

Here I have an interface called “ifcfg-eth0“, the default interface for the Ethernet device. If you’ve attached second Ethernet device, then there would be an “ifcfg-eth1” device and so on for each device you’ve attached. These device network files are located in “/etc/sysconfig/network-scripts/” directory. Navigate to the directory and do “ls -l” to list all devices.

# cd /etc/sysconfig/network-scripts/
# ls -l
Sample Output
ifcfg-eth0   ifdown-isdn    ifup-aliases  ifup-plusb     init.ipv6-global
ifcfg-lo     ifdown-post    ifup-bnep     ifup-post      net.hotplug
ifdown       ifdown-ppp     ifup-eth      ifup-ppp       network-functions
ifdown-bnep  ifdown-routes  ifup-ippp     ifup-routes    network-functions-ipv6
ifdown-eth   ifdown-sit     ifup-ipv6     ifup-sit
ifdown-ippp  ifdown-tunnel  ifup-isdn     ifup-tunnel
ifdown-ipv6  ifup           ifup-plip     ifup-wireless

Let’s assume that we want to create three additional virtual interfaces to bind three IP addresses (172.16.16.126, 172.16.16.127, and 172.16.16.128) to the NIC. So, we need to create three additional alias files, while “ifcfg-eth0” keeps the same primary IP address. This is how we moving forward to setup three aliases to bind the following IP addresses.

Adapter            IP Address                Type
-------------------------------------------------
eth0              172.16.16.25            Primary
eth0:0            172.16.16.26            Alias 1
eth0:1            172.16.16.27            Alias 2
eth0:2            172.16.16.28            Alias 3

Where “:X” is the device (interface) number to create the aliases for interface eth0. For each alias you must assign a number sequentially. For example, we copying existing parameters of interface “ifcfg-eth0” in virtual interfaces called ifcfg-eth0:0, ifcfg-eth0:1 and ifcfg-eth0:2. Go into the network directory and create the files as shown below.

# cd /etc/sysconfig/network-scripts/
# cp ifcfg-eth0 ifcfg-eth0:0
# cp ifcfg-eth0 ifcfg-eth0:1
# cp ifcfg-eth0 ifcfg-eth0:2

Open a file “ifcfg-eth0” and view the contents.

[root@tecmint network-scripts]# vi ifcfg-eth0

DEVICE="eth0"
BOOTPROTO=static
ONBOOT=yes
TYPE="Ethernet"
IPADDR=172.16.16.125
NETMASK=255.255.255.224
GATEWAY=172.16.16.100
HWADDR=00:0C:29:28:FD:4C

Here we only need two parameters (DEVICE and IPADDR). So, open each file with VI editor and rename the DEVICE name to its corresponding alias and change the IPADDR address. For example, open files “ifcfg-eth0:0“, “ifcfg-eth0:1” and “ifcfg-eth0:2” using VI editor and change both the parameters. Finally it will look similar to below.

ifcfg-eth0:0
DEVICE="eth0:0"
BOOTPROTO=static
ONBOOT=yes
TYPE="Ethernet"
IPADDR=172.16.16.126
NETMASK=255.255.255.224
GATEWAY=172.16.16.100
HWADDR=00:0C:29:28:FD:4C
ifcfg-eth0:1
DEVICE="eth0:1"
BOOTPROTO=static
ONBOOT=yes
TYPE="Ethernet"
IPADDR=172.16.16.127
NETMASK=255.255.255.224
GATEWAY=172.16.16.100
HWADDR=00:0C:29:28:FD:4C
ifcfg-eth0:2
DEVICE="eth0:2"
BOOTPROTO=static
ONBOOT=yes
TYPE="Ethernet"
IPADDR=172.16.16.128
NETMASK=255.255.255.224
GATEWAY=172.16.16.100
HWADDR=00:0C:29:28:FD:4C

Once, you’ve made all changes, save all your changes and restart/start the network service for the changes to reflect.

[root@tecmint network-scripts]# /etc/init.d/network restart

To verify all the aliases (virtual interface) are up and running, you can use “ifconfig” or “ip” command.

[root@tecmint network-scripts]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0C:29:28:FD:4C
          inet addr:172.16.16.125  Bcast:172.16.16.100  Mask:255.255.255.224
          inet6 addr: fe80::20c:29ff:fe28:fd4c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:237 errors:0 dropped:0 overruns:0 frame:0
          TX packets:198 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:25429 (24.8 KiB)  TX bytes:26910 (26.2 KiB)
          Interrupt:18 Base address:0x2000

eth0:0    Link encap:Ethernet  HWaddr 00:0C:29:28:FD:4C
          inet addr:172.16.16.126  Bcast:172.16.16.100  Mask:255.255.255.224
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:18 Base address:0x2000

eth0:1    Link encap:Ethernet  HWaddr 00:0C:29:28:FD:4C
          inet addr:172.16.16.127  Bcast:172.16.16.100  Mask:255.255.255.224
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:18 Base address:0x2000

eth0:2    Link encap:Ethernet  HWaddr 00:0C:29:28:FD:4C
          inet addr:172.16.16.128  Bcast:172.16.16.100  Mask:255.255.255.224
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:18 Base address:0x2000
Posted in Uncategorized | Leave a comment

Manually truncate Exchange logs

ometimes your Exchange backup just doesn’t seem to get around to truncating the log.  You can’t turn on circular logging because it prevents using differential and incremental backups.  What is a tech supposed to do?

Truncate the Exchange transaction logs manually.  Here’s how.

  1. Login to the Exchange mailbox server.
  2. Open the Exchange management shell (EMS).
  3. Open the Exchange management console (EMC).
  4. In the EMC, stop the database that you want to truncate the logs for.
  5. In EMS, run the command
    eseutil /MH “M:\Database Path\Mailbox store.edb”
  6. In the output, it will tell you what the database state is.  If it says “Clean Shutdown”, you can move all of the logs to another directory.  The logs you want to move start with EDB followed by a 5 digit hexadecimal number.
  7. In the EMS, start the database and test.

Typically, I save the logs for 12 hours before I delete them permanently, but I may be overly cautious.

Posted in Exchange | Leave a comment