Заметки сисадмина о интересных вещах из мира IT, инструкции и рецензии. Настраиваем Компьютеры/Сервера/1С/SIP-телефонию в Москве


Page 1 of 21612345...Last »

503 error on vCSA 6.5.0a running on ESXi 6.5.0a

2017-03-23 · Posted in VMWare

So, I opened a case with VMware and it’s a known issue for vCenter 6.5.0a. The below fix directly solved the error I was seeing.

Information attached for reference only. Please be aware that this may NOT be applicable to your system and may bork it completely!

Symptoms

On the webclient, the web page shows the error: 503 Service Unavailable (Failed to connect to endpoint). . .

PowerCLI cannot connect to vCenter.

vpxd on vCenter Server 6.5 intermittently crashes with the following error stack in the vpxd log file:

 Note:

  • The VMware vCenter Server 6.5 vpxd logs are located in the %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\vmware-vpx folder.
  • The VMware vCenter Server Appliance vpxd 6.5 logs are located in the /var/log/vmware/vmware-vpx folder.

 Resolution

Caution: Before making database modifications, ensure there is a working backup of the database or snapshot.

 If the embedded postgres database is being used, locate the duplicate key in the postgresql logs:

 postgresql.log

 Note: The postgresql.log  can be found in var/log/vmware/vpostgres

 To connect to the embedded postgres database:

To remove the duplicate key run the below command:

(modify the id and device_key according to your vpxd log below!):

Step-by-Step Guide for upgrading SYSVOL replication to DFSR (Distributed File System Replication)

2017-03-08 · Posted in Active Directory

SYSVOL is a folder shared by domain controller to hold its logon scripts, group policies and other items related to AD. All the domain controllers in network will replicate the content of SYSVOL folder. The default path for SYSVOL folder is %SystemRoot%SYSVOL. This folder path can define when you install the active directory.

Windows Server 2003 and 2003 R2 uses File Replication Service (FRS) to replicate SYSVOL folder content to other domain controllers. But Windows server 2008 and later uses Distributed File System (DFS) for the replication.  DFS is more efficient than FRS. Since windows server 2003 is going out of support, most people already done or still looking for migrate in to latest versions. However migrating FSMO roles WILL NOT migrate SYSVOL replication from FRS to DFS. Most of the engineers forget about this step when they migrate from windows 2003 to new versions.

For FRS to DFS migration we uses the Dfsrmig.exe utility. More info about it available on https://technet.microsoft.com/en-au/library/dd641227(v=ws.10).aspx

For the demo I am using windows server 2012 R2 server and I migrated FSMO roles already from a windows server 2003 R2 server.

In order to proceed with the migration forest function level must set to windows server 2008 or later. So if your organization not done this yet first step is to get the forest and domain function level updated.

You can verify if the system uses the FRS using dfsrmig /getglobalstate , To do this

1)    Log in to domain controller as Domain admin or Enterprise Admin
2)    Launch powershell console and type dfsrmig /getglobalstate. Output explains it’s not initiated DFRS migration yet.

dfrs1

Before move in to the configurations we need to look into stages of the migration.

There are four stable states going along with the four migration phases.

1)    State 0 – Start
2)    State 1 – Prepared
3)    State 2 – Redirected
4)    State 3 – Eliminated

State 0 – Start

With initiating this state, FRS will replicate SYSVOL folder among the domain controllers. It is important to have up to date copy of SYSVOL before begins the migration process to avoid any conflicts.

State 1 – Prepared

In this state while FRS continues replicating SYSVOL folder, DFSR will replicate a copy of SYSVOL folder. It will be located in %SystemRoot%SYSVOL_DFRS by default. But this SYSVOL will not response for any other domain controller service requests.

State 2 – Redirected

In this state the DFSR copy of SYSVOL starts to response for SYSVOL service requests. FRS will continue the replication of its own SYSVOL copy but will not involve with production SYSVOL replication.

State 3 – Eliminated

In this state, DFS Replication will continue its replication and servicing SYSVOL requests. Windows will delete original SYSVOL folder users by FRS replication and stop the FRS replication.

In order to migrate from FRS to DFSR its must to go from State 1 to State 3.

Let’s look in to the migration steps.

Prepared State

1.    Log in to domain controller as Domain admin or Enterprise Admin
2.    Launch powershell console
3.    Type dfsrmig /setglobalstate 1 and press enter

dfrs2

4.    Type dfsrmig /getmigrationstate to confirm all domain controllers have reached prepared state

dfrs3

Redirected State

1.    Log in to domain controller as Domain admin or Enterprise Admin
2.    Launch powershell console
3.    Type dfsrmig /setglobalstate 2 and press enter

dfrs4

4.    Type dfsrmig /getmigrationstate to confirm all domain controllers have reached redirected state

dfrs5

Eliminated State

1.    Log in to domain controller as Domain admin or Enterprise Admin
2.    Launch powershell console
3.    Type dfsrmig /setglobalstate 3 and press enter

dfrs6

4.    Type dfsrmig /getmigrationstate to confirm all domain controllers have reached eliminated state

dfrs7

This completes the migration process and to confirm the SYSVOL share, type net share command and enter.

dfrs8

Also make sure in each domain controller FRS service is stopped and disabled.

dfrs9

Загрузка ОКОФ в 1С:Бухгалтерия 8.3 (редакция 3.0)

Общероссийский классификатор основных фондов (ОКОФ) создан для классификации основных средств в организациях, предприятиях и учреждениях всех форм собственности. По умолчанию в 1С:Бухгалтерия 8.3 справочник ОКОФ не заполнен. Для его загрузки необходимо выполнить инструкции, описанные ниже.

1. Скачайте архив с классификатором ОКОФ по следующей ссылке на рабочий стол.

2. Внутри этого архива – файл okof.xml. Распакуйте (вытащите) этот файл на рабочий стол.

3. Откройте меню “Все функции”.  Если у вас отсутствует данный пункт – вам сюда

Как загрузить ОКОФ в 1С БУхгалтерия 8.3 (редакция 3.0) №1

4. В открывшемся окне раскройте список справочников (плюсик слева).

Как загрузить ОКОФ в 1С БУхгалтерия 8.3 (редакция 3.0) №2

5. Среди справочников выберите “Классификатор ОКОФ” и нажмите кнопку “Открыть”.

Как загрузить ОКОФ в 1С БУхгалтерия 8.3 (редакция 3.0) №3

6. Открылся классификатор ОКОФ. Как видите он пуст. Нажмите кнопку “Загрузить классификатор ОКОФ”.

Как загрузить ОКОФ в 1С БУхгалтерия 8.3 (редакция 3.0) №4

7. Открылось окно загрузки. Нажмите кнопку “Открыть файл..” и выберите скачанный на первом шаге файл okof.xml на рабочем столе.

Как загрузить ОКОФ в 1С БУхгалтерия 8.3 (редакция 3.0) №5

8. Нажмите кнопку “Загрузить данные”.

Как загрузить ОКОФ в 1С БУхгалтерия 8.3 (редакция 3.0) №6

9. Дождитесь окончания загрузки и нажмите кнопку “Закрыть”.

Как загрузить ОКОФ в 1С БУхгалтерия 8.3 (редакция 3.0) №7

10. Готово! Закройте и откройте снова справочник “Классификатор ОКОФ” и увидите, что он полностью заполнен и готов к использованию!

Как загрузить ОКОФ в 1С БУхгалтерия 8.3 (редакция 3.0) №8

Page 1 of 21612345...Last »