Các bài viết cũ

SharePoint nâng cao: Phần 5 – Cấu hình hệ thống báo cáo động và dịch vụ báo cáo trên SharePoint 2010


1.  Cấu hình hệ thống Báo cáo Report Services:

image

 

2. Download phần mềm Microsoft® SQL Server® 2008 R2 Reporting Services Add-in for Microsoft SharePoint® Technologies 2010

Link download: http://www.microsoft.com/en-us/download/details.aspx?id=622

Bấm click đúp vào rsSharePoint để chạy.

image

 

3. Các bước cài Reporting Services Add-in for SharePoint 2010

image

 

image

 

image

 

image

 

4. Kiểm tra tình trạng hoạt động của Report Services:

image

 

Chúc các bạn thành công !

Kết thúc phần 5 – các bạn sẽ dựng được toàn bộ hệ thống Report service tích hợp từ MS SQL Server 2008 R2 sang với giao diện, webpart và Report Design thiết kế báo cáo động trên web (một phần nền tảng công cụ hỗ trợ phát triển Business Intelligent – B).

Mời các bạn đón đọc phần tiếp theo – SharePoint nâng cao – Phần 6: Phát triển Development Dashboard trên máy chủ SharePoint 2010

Advertisements

USB được chỉ định truy cập trên máy tính Windows 7/8.x


1. Phương án 1:

Thay vì quy định cho ổ USB chỉ định được truy cập vào cổng USB trên máy PC, ta có thể tùy chỉnh cho những User nào có quyền mới được truy cập vào cổng USB, các bước tiến hành như sau:

Bước 1: Start Window Expoler và tìm kiếm như sau:”%SystemRoot%Inf

image

Bước 2: Tìm đến thư mục Usbtor.PNF và chuột phải vào file chọn Properties:

image

Bước 3: Thẻ tùy chỉnh được mở ra, chọn Tab sercurity

image

Chú ý: ta cũng có thể cho tài khoản thuộc hệ thống AD Domain/LDAP vào danh sách Deny Permission

Bước 4: Đối với file Usbtor.INF ta cũng sẽ làm tương tự:

image

Bước 5. Kiểm tra sau khi đặt lại quyền cho các users và groups trong 2 files nói trên, ta có thể tùy chỉnh cho những User và Group được chỉ định mới có thể truy cập vào cổng USB.

2. Phương Án 2: sử dụng Bit-locker

Bước 1. Ta cắm USB vào cổng USB của máy tính, bấm chuột phải vào ổ USB cần mã hóa chọn Turn on bitlocker.

image

Bước 2. Hộp thoại mã hóa Bitlocker sẽ mở ra, có 2 các thức để mở khóa ổ đĩa (khi đã bị mã hóa, cách 1. Dùng mật khẩu, cách 2. Dùng TPM card)

image

Nhằm đáp ứng yêu cầu ta sẽ chọn cách dùng mật khẩu,Ta sẽ nhập Mật khẩu vào bên dưới (mật khẩu để mở các thư mục sau khi đã mã hóa…..)

Bước 3. Sau khi thiết lập mật khẩu bạn sẽ được cung cấp 1 file khóa “cứng” khôi phục mật khẩu khi bị mất hoặc quên mật khẩu…

image

Bước 4. Tiếp theo bạn bấm next để bắt đầu mã hóa ổ đĩa:image

Sau khi quá trình kết thúc một hộp thoại thông báo hoàn thành sẽ được mở ra:

image

Lưu ý: Kích thước để mã hóa và có mật khẩu tối thiểu 64Mb và không lên lớn quá 64Gb vì sẽ mất thời gian lâu để giải mã khi cần truy cập.

Bước 5. Sau khi hoàn thành ta sẽ có USB được Cài mật khẩu:

image

Khi mở sẽ yêu cầu mật khẩu:Chú ý mỗi lần cắm USB sẽ bị yêu cầu nhập Password để mở.

image

Cách cấu hình SMTP Relay trên máy chủ IIS–Windows 2008 kết nối Exchange Online của Office 365


Cấu hình SMTP Relay trên máy chủ IIS 7, 7.5 Windows Server 2008

Contents

1. Mở IIS 7. 1

2. Kích hoạt SMTP Server trên máy chủ Windows 2008. 2

3. Cấu hình SMTP trên IIS 6. 3

4. Kiểm tra chạy cấu hình SMTP trên IIS 6. 9

5. Cấu hình Mail trên SharePoint Administrator Center. 10

1. Mở IIS 7

clip_image002

2. Kích hoạt SMTP Server trên máy chủ Windows 2008

clip_image004

3. Cấu hình SMTP trên IIS 6

clip_image006

clip_image008

clip_image010clip_image012

clip_image014

clip_image016clip_image018clip_image019clip_image021

Cách xác định địa chỉ máy chủ Exchange Online bằng lệnh CMD như sau:

clip_image023

Ví dụ: địa chỉ mail.cloud.edu.vn là địa chỉ bạn đã khai subdomain / DNS của webmail theo nhà cung cấp dịch vụ quản lý tên miền

Kết quả trả về là màn thông báo kết nối thành công mã 220

clip_image025

Cuối cùng, mở Start\Control Panel\Services kiểm tra dịch vụ SMTP đã started.

clip_image027

4. Kiểm tra chạy cấu hình SMTP trên IIS 6

Tạo 1 file có tên mail.txt, có nội dung sau:

From:<thang.le@hotmail.com>

To:<youremail@your_domain_office365.edu.vn>

Subject: Test mail from IIS Server via SMTP Relay Office 365

Body:

Mail Content to send SMTP Relay.

^

Hãy copy file này vào thư mục c:\inetpub\mailroot\pickup\

clip_image029

Nếu hệ thống chạy tốt, cấu hình SMTP trong IIS đúng, file đó sẽ tự động chuyển sang thư mục Queu và Send, bạn có thể kiểm tra log của IIS 6 hoặc trên hòm thư bạn đã gửi trong mục To:<> của nội dung file mail.txt.

5. Cấu hình Mail trên SharePoint Administrator Center

clip_image031

Cách chuyển từ 1 file chạy EXE sang dạng Windows Service


Converting lhwsrv.exe to a Windows Service

You can convert lhwsrv.exe to a Windows Service by following the following steps. However this involves

  • using a Command Prompt (aka DOS box)
  • changing you PATH
  • editing your registry
  • fooling with Services

These are not for the faint of heart nor for those not familiar with Registry hacking and DOS boxes. Of course you should back up your system and your Registry before beginning – if you don’t know how to do these, click your Back button now. Also this probably only works for Win/XP and Win/Vista – if you have an older operating system, click your Back button now.

 

  1. Download and install the Windows Server 2003 Toolkit. You may have to search microsoft.com for it, but when I wrote this page, it resided at http://www.microsoft.com/downloads/details.aspx?FamilyID=9D467A69-57FF-4AE7-96EE-B18C4790CFFD&displaylang=en. Of course the best way to search microsoft.com is via Google – try this: Google Windows Server 2003 Toolkit.
  2. Win/Vista will complain about compatibility issues – ignore that and go ahead with the install – the 2 programs you need work fine on Vista (if you have sufficient privileges).
  3. Open a DOS box: Click Start > Run (or maybe Search for Vista) and enter cmd & click the OK button. SC_VCE Testing System1
  4. Change to the directory when you installed the Windows Server 2003 Toolkit. If you took the defaults during installation, use the following:
  5. C:\Windows>cd C:\Program Files (x86)\Windows Resource Kits\Tools
  6. Run the following command where “C:\Program Files\Windows Resource Kits\Tools” should be replaced with the directory where you installed the Windows Server 2003 Toolkit:
  7. C:\Program Files\Windows Resource Kits\Tools>instsrv.exe lhwsrv “C:\Program Files (x86)\Windows Resource Kits\Tools\srvany.exe”
  8. The Toolkit install with have added C:\Program Files (x86)\Windows Resource Kits\Tools to your Path as the first directory. You will want to remove it (or at least move it). Bring up the Control Panel (Start > Settings > Control Pannel) and double-click the System applet. Find the “Advanced” Tab or “Advanced System Settings” link and click it; then click the Environment Variables button. Scroll down the Environment Variables list in the lower path of the dialog until you find the Path variable. Click Edit, press the Home key, and remove the Toolkit path from the beginning of the value. Click OK all the way out. You must remove the Toolkit from your PATH for Windows/Vista since many of the programs don’t work on Vista; you might want to keep it for Win/XP, but do so only if you are sure of what you are doing.
  9. Fire up RegEdit. You can do so by trying the regedit at the DOS box command prompt:
      C:\Program Files (x86)\Windows Resource Kits\Tools>regedit
  10. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lhwsrv
  11. Right click on lhwsrv and click select ‘new‘ then ‘key.’ Name the new key ‘Parameters‘.
  12. Now double click the Parameters key and right click on the empty space in the right hand pane. Choose ‘new‘ then ‘string value‘. Name the new value ‘Application‘.
  13. Now repeat the last step, this time naming the string value ‘AppDirectory‘.
  14. Double click on ‘Application‘ and give it the location of lhwsrv.exe. For example, if you placed lhwsrv.exe in the c:\bin\ directory, you would type ‘c:\bin\lhwsrv.exe‘.
  15. Double click on ‘AppDirectory‘ and give it the location of the directory where your lhwsrv.exe can be found. Using the above example, the value here would be ‘c:\bin\’
  16. Your Registry should now look something like this (don’t worry if the Enum key is not present):

    Your Data will of course be where you have placed lhwsrv.exe rather than c:\l-drive\bin.

  17. You can now close RegEdit.
  18. Fire up the Services applet. You can get to this via Start > Settings > Control Panel. Then look for a Services Applet either in the main window or perhaps in Administrative Tools. You can even try running services.msc or services.exe at your command prompt.
  19. Find lhwsrv in the list and double-click it.
  20. It should look like this (Note that the Path to executable value is listed as C:\Program Files (x86)\Windows Resource Kits\Tools\srvany.exe. This is because the srvany file is acting as a carrier for the executable file of the program you chose.):

    Set the Startup Type to Automatic and click Start if necessary and you are done.

How To Create a User-Defined Service or How to create a Windows service by using Sc.exe


The Windows NT Resource Kit provides two utilities that allow you to create a Windows NT user-defined service for Windows NT applications and some 16-bit applications (but not for batch files).
Instrsrv.exe installs and removes system services from Windows NT and Srvany.exe allows any Windows NT application to run as a service.

 

To create a Windows NT user-defined service, perform the following steps:

  1. At a MS-DOS command prompt(running CMD.EXE), type the following command:
    path\INSTSRV.EXE My Service path\SRVANY.EXE
    where path is the drive and directory of the Windows NT Resource Kit (i.e., C:\RESKIT) and My Service is the name of the service you are creating.
    Example:

    C:\Program Files\Resource Kit\Instsrv.exe Notepad C:\Program Files\Resource Kit\Srvany.exe

    NOTE: To verify that the service was created correctly, check the registry to verify that the ImagePath value under

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\service name

    is set to point to SRVANY.EXE. If this is not set correctly, the service will stop shortly after it starts and return an Event ID 7000 “The service name failed to start.”
    WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
    For information about how to edit the registry, view the “Changing Keys And Values” online Help topic or the “Add and Delete Information in the Registry” and “Edit Registry Data” online Help topics in Registry Editor.
    NOTE: You should back up the registry before you edit it.

  2. Run Registry Editor (Regedt32.exe)and locate the following subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<My Service>
  3. From the Edit menu, click Add Key. Type the following and click OK:
    Key Name: Parameters
    Class : <leave blank>
  4. Select the Parameters key.
  5. From the Edit menu, click Add Value. Type the following and click OK:
    Value Name: Application
    Data Type : REG_SZ
    String : <path>\<application.ext>
    where <path>\<application.ext> is the drive and full path to the application executable including the extension (i.e., C:\WinNT\Notepad.exe)
  6. Close Registry Editor.

By default, a newly created service it configured to run Automatically when the system is restarted. To change this setting to Manual, run the Services applet from Control Panel and change the Startup value to Manual. A service set to Manual can be started in one of several ways:

– From the Services applet in Control Panel
– From a MS-DOS command prompt, type the following:
NET START <My Service>
– Use the Sc.exe utility from the Resource Kit. Type the following from a MS-DOS command prompt:
<path>\Sc.exe start <My Service>
where <path> is the drive and directory of the Windows NT Resource Kit (i.e., C:\Reskit).

For more information on installing and removing a user-defined service, please see the Srvany.wri document provided with the Windows NT Resource Kit utilities (i.e., C:\Reskit\Srvany.wri). This document can also be found on the Windows NT Resource Kit CD in the Common\Config directory.

 

 

How to create a Windows service by using Sc.exe

To remotely create and start a service from the command line, you can use the SC tool (Sc.exe) included in the Resource Kit.
Although you can use the Netsvc.exe and Instsrv.exe tools to start a service on a remote computer, these tools do not give you the ability to remotely create a service.
Note The Srvinstw.exe tool is the graphical user interface (GUI) version used to create remote services. Srvinstw.exe is not a command-line tool.

 

You can use Sc.exe to help develop services for Windows. Sc.exe, which is provided in the Resource Kit, implements calls to all of the Windows service control application programming interface (API) functions. You can set the parameters to these functions by specifying them on the command line. Sc.exe also displays service status and retrieves the values stored in the status structure fields. The tool also lets you specify the name of a remote computer so that you can call the service API functions or view the service status structures on the remote computer.
Sc.exe also allows you to call any of the service control API functions and vary any of the parameters from the command line. The advantage to this is that it provides a convenient way to create or configure the service information in the registry and the Service Control Manager database. You do not have to configure the service by manually creating entries in the registry and then restarting the computer to force the Service Control Manager to update its database.
Sc.exe uses the following syntax:
Syntax1 (use Syntax1 to run Sc.exe)

sc [Servername] Command Servicename [Optionname= Optionvalue…]

Syntax2 (use Syntax2 to display help information, except for the query command)

sc [Command]

Parameters
  • Servername
    Optional. Specifies the name of the server when you want to run the commands on a remote computer. The name must start with two backslash (\) characters (for example, \\myserver). To run Sc.exe on the local computer, do not supply this parameter.
  • Command
    Specifies the sc command. Note that many of the sc commands require administrative privileges on the specified computer. Sc.exe supports the following commands:

    Config
    Changes the configuration of a service (persistent).
    Continue
    Sends a Continue control request to a service.
    Control
    Sends a control to a service.
    Create
    Creates a service (adds it to the registry).
    Delete
    Deletes a service (from the registry).
    EnumDepend
    Enumerates service dependencies.
    GetDisplayName
    Obtains the DisplayName for a service.
    GetKeyName
    Obtains the ServiceKeyName for a service.
    Interrogate
    Sends an Interrogate control request to a service.
    Pause
    Sends a Pause control request to a service.
    qc
    Queries configuration for the service. For detailed information, see the reference section, “SC QC.”
    Query
    Queries the status for a service, or enumerates the status for types of services. For detailed information, see the reference section, “SC QUERY.”
    Start
    Starts a service
    Stop
    Sends a Stop request to a service.

  • Servicename
    Specifies the name given to the Service key in the registry. Note that this is different from the display name (which is what you see with net start command and the Services tool in Control Panel. Sc.exe uses the service key name as the primary identifier for the service.
  • Optionname
    The Optionname and Optionvalue parameters allow you to specify the names and values of optional command parameters. Note that there is no space between the Optionname and the equal sign. You can supply none, one, or more optional parameters name and value pairs.
  • Optionvalue
    Specifies the value for the parameter named by Optionname. The range of valid values is often restricted for each Optionname. For a list of available values, request help for each command.

Many of the commands require Administrator privileges. Make sure that you are an administrator of the computer where the development is being performed.
The sc create command creates an entry for the service in the registry and in the Service Control Manager database.
Syntax

sc [Servername] create Servicename [Optionname= Optionvalue…

Parameters
  • Servername
    Optional. Specifies the name of the server when you want to run the commands on a remote computer. The name must start with two backslash characters (for example, \\myserver). To run SC on the local computer, do not supply this parameter.
  • Servicename
    Specifies the name given to the service key in the registry. Note that this is different from the display name, which is what you see with net start and the Services tool in Control Panel. Sc.exe uses the service key name as the primary identifier for the service.
  • Optionname
    The Optionname and Optionvalue parameters allow you to specify the names and values of optional parameters. Note that there is no space between the Optionname and the equal sign. You can supply none, one, or more optional parameters name and value pairs. The sc query command supports the following values:OptionnameOptionvalue

    type=own, share, interact, kernel, filesys
    Type of service you want to create. Optionvalues include types used by drivers.
    (default = share)
    start=boot, system, auto, demand, disabled
    Start type for the service. Option values include types used by drivers.
    (default = demand)
    error=normal, severe, critical, ignore
    Severity of error if the service does not start during boot.
    (default = normal)
    binPath=(string)
    Path name to the service binary file. There is no default for this parameter. This string must be supplied.
    group=(string)
    Name of group which this service is a member of. The list of groups are stored in the registry under ServiceGroupOrder.
    (default = nothing)
    tag=(string)
    If this string is set to “yes,” Sc.exe obtains a TagId from the CreateService call, however, Sc.exe does not display the tag.
    (default = nothing)
    depend=(space separated string)
    Names of services or groups that must start before this service.
    obj=(string)
    Name of account in which the service runs. For drivers, this is the Windows driver object name.
    (default = LocalSystem)
    DisplayName=(string)
    A string that can be used by user-interface programs to identify the service.
    password=(string)
    A password string. This is required if an account other than LocalSystem is used.

Optionvalue
Specifies the value for the parameter named by Optionname. See the Optionname reference for a list of supported values. When a string is to be input, the use of empty quotes means that an empty string is passed in. Note that there is a space between OptionValue and the equal sign.
Note The sc create command performs the operations of the CreateService API function.
The following example creates a registry entry for the service named “NewService” on the computer called \\remotecomputer:

sc \\remotecomputer create newservice binpath= c:\nt\system32\newserv.exe

Note In Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008, the binpath is located at C:\Windows\System32\Newserv.exe.
This service is created as a WIN32_SHARE_PROCESS with a SERVICE_DEMAND_START start-type by default. It does not have any dependencies, and runs in the LocalSystem security context.
The following example creates the service on the local computer as an auto-start service that runs in its own process. It has dependencies on the TDI group and on the NetBIOS service. Notice that you must add quotes around the list of space-separated dependencies.

sc create newservice binpath= c:\nt\system32\newserv.exe type= own start= auto depend= “+tdi netbios”

Note In Windows 2000, Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008, the binpath is located at C:\Windows\System32\Newserv.exe.
For further details about the Sc.exe tool, please see the Sc-dev.txt document in the Resource Kit. This document describes Sc.exe in greater detail.

 

At the time of this posting, there is no Windows Server 2008 Resource Kit Tools, so get the “srvany.exe ” from the “Windows Server 2003 Resource Kit Tools ” and copy it to a suitable location on your Win2008 server (e.g. C:\Windows\System32\ ).
Use “sc ” to create a new service that launches “srvany ” (e.g. sc create MyService binPath= C:\Windows\System32\srvany.exe DisplayName= “My Custom Service” )
Using RegEdit : create a “Parameters ” key for your service (e.g. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MyService\Paramaters\ )
Using RegEdit : within the newly created “Parameters ” key , create a string value called “Application ” and enter the full path to the application you are wanting to run as a service. (No quotes required.)

And that should do it.

Note : some applications store their settings in a user hive, not under HKEY_LOCAL_MACHINE, so you will need to run the application to configure it, and then configure the service to run as that user.

 

 

Ví dụ: chạy CMD

gõ lệnh: sc create “VCE Testing System” start= auto binpath= ”c:\blabla\VCE Testing\server.exe”

 

 

Sau khi chạy lệnh SC trên, bạn cần tạo đăng ký trên WIndows Registry Editor Version

 

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VCE Testing System\Paramaters]

“Application”=”c:\\blabla\\VCE Testing\\server.exe”

 

Hoặc cách 2: dùng các tool phần mềm miễn phí

ví dụ: http://tools.sysprogs.org/srvman/

Cách tạo chữ ký số SSL cho HTTPS của IIS 7.5 theo dạng SAN (multiple Domain)


1. How to create a SAN certificate signing request for IIS web server?

  • Open Certificate MMC snap in for your computer

    • Click on Start – Run – MMC – File – Add/Remove Snap In – Select Certificates – Click Add – Select My Computer
  • Click on Personal – All Tasks – Advanced Operations – Create Custom request

  • Click next in Certificate Enrollment Wizard’s welcome window
  • Select “Proceed without enrollment policy” under Custom Request & click next
  • In Custom Request window Select (No template) Legacy key & PKCS #10 as request format
  • And Click Next

  • In Certificate Information Page click the Details icon then Properties. It will open up Certificate Properties window, where we can define different attributes.

  • Under Private Key, select key size. Over here I just left it as default. You may like to select 4096 for production servers.
  • Under Key Type select “Exchange

  • Under Extension tab select Extended Key Usage; add Server Authentication from the available options.

  • Under Subject Tab we will be defining our multiple DNS names for the certificate
  • From Drop down Subnet Name section select Common Name & type the value. Preferably the primary domain name & then click Add.
  • Under Alternative Name select DNS type all alternate DNS Names & add them.

  • Under General Tab type a friendly name.
  • Better to keep add a * in front of the friendly name now. It will help you to bind the certificate from IIS graphical user interface to all websites using same IP & port 443. If you don’t do this now, no worries, you can do it later or you can use Commadline tool to bind this cert. I have discussed the same in certificate installation/import post.
  • Click okay & In certificate information window click next

  • Give a file path to save this certificate request 7 select Base 64 as file format

  • It will generate “.req” file, you can open this file using notepad.
  • You use this file to generate your SAN certificate from external public certificate authority or from your internal certificate authority server.
    2. Certificate Requests in Windows Server 2008
Submit Certificate Request

For requests submitted to a public CA simply copy/paste the text from the generated file to that CA’s request form and then wait for the completed .cer file to be sent back and then skip to the next section

image

But for internal requests there are multiple ways to submit them to a Windows CA. Depending on the tools and permissions available some of these approaches may not work in certain environments. If access is prevented for certificate submissions then send the request text file to the appropriate personnel and wait for them to send back the certificate file, then jump to the next section to complete the request.

Assuming that both connectivity to the CA and the appropriate permissions are available then follow these basic steps to submit the request to the Windows CA using certreq.exe from the standard Windows command prompt.

  • From the same server open the standard Windows Command Prompt. (If network connectivity to the CA is not available from this host then copy the request file to the CA server or anther Windows server with access and run these commands from that system.)

Change to the current directory where the new request file was saved (e.g. C:\Temp) and issue the following command:

certreq.exe -submit -attrib “CertificateTemplate:WebServer” newcert.req newcert.cer

The CertificateTemplate attribute can be used to supply the name of whatever the custom template’s name is in the CA, assuming that template was configured in a way that is still compatible with the type of request generated.

In the Certification Authority List pop-up window select the desired Windows CA to submit the request against.

image

The results of the command should indicate a successful request and the resulting certificate file will be written to a new text file in the same directory as indicated in the command (newcert.cer).

image

As the Request ID is displayed in the output above, then the details of the issued certificate can be verified on the CA itself by opening the Certificate Authority administrative tool on the CA server and then browsing to the Issued Certificates container to look for the matching ID.

image

Complete Certificate Request

Before completing the request locate and open the newly generated certificate file (newcert.cer). Notice that the private key description is missing from the General tab information.

Although this appears to look like a ‘certificate’ file it is actually just the public key portion that is generated by the CA, the all-important private key portion is still stored locally on the requesting server and the two items need to be joined together to create an actual functioning certificate pair. Without a valid private key nothing can be decrypted which was encrypted using the public key.

image

Although this appears to look like a ‘certificate’ file it is actually just the public key portion that is generated by the CA, the all-important private key portion is still stored locally on the requesting server and the two items need to be joined together to create an actual functioning certificate pair. Without a valid private key nothing can be decrypted which was encrypted using the public key.

  • From the Action pane of Internet Information Services (IIS) Manager select Complete Certificate Request.

image

  • In the Specify Certificate Authority Response window browse for and select the certificate file (newcert.cer) and provide a Friendly Name for the certificate, then complete the wizard.

image

View the properties of the new certificate and this time the General information will indicate that the private key has successfully been linked to the new certificate.

image

BIS 2012 con đường cho giải pháp Business Intelligence và SharePoint Web Application


Khái lược:

Sau 12 năm nghiên cứu và xây dựng hệ thống BI bằng các phương án cổ điển như: Visual Basic  để thiết lập môi trường AW Ad-Hoc Reporter bằng Windows Form

Mô hình sản phẩm nhằm thiết lập Hệ thống báo cáo báo biểu đã được Microsoft phát triển từ thập niên 90:

BIS_Production

Tham khảo bài viết: https://thangletoan.wordpress.com/2013/07/30/lap-trnh-aw-ad-hoc-reporter-lm-bo-co-rdl-trong-sql-server-2008-r2/

Các sản phẩm và công nghệ BI tôi đã nghiên cứu và thiết kế trải dài hơn 13 năm qua được thể hiện:

  1. 1995: VISData 1.0
  2. 1998: VISData 1.1
  3. 2001: VASEPData 2.0
  4. 2003: PSMS Data 3.0
  5. 2004: WCOO Customs DB 1.0
  6. 2005: VN Customs Data 3.1
  7. 2008: Spanish Customs Data 2.0
  8. 2010: VN Customs DB 4.0
  9. 2013: Global Customs BIS 2012

Và vừa qua tôi đã có cơ hội để thể hiện một quan điểm, một cách nhìn đổi mới, một con đường phát triển công nghệ ứng dụng giải pháp mới cho toàn bộ

mạng lưới:

–  WCOO – ECC (Hải quan Châu âu)

– FIGIS (Tổ chức liên minh các Chuyên gia Nghiên cứu phân tích Kinh tế liên hợp quốc )

– FAO (Tổ chức nông lương thế giới)

– FIIS (Phòng kinh tế Thuỷ sản)

BIS2012

Kết quả:

– Sự thành công là chắc chắn vì nó là sự nghiệp, đam mê nghiên cứu và ứng dụng thực tiễn của tôi, của cả một đội ngũ các chuyên gia phân tích, thống kê quốc tế.

– Trong đó vai trò: Công nghệ Microsoft BI góp một phần rất quan trọng trong đường lối tư duy “Đổi mới” để giải quyết các  bài toán về Big Data vô cùng cấp thiết, phức tạp và quan trọng.

– Thay đổi trên đây mang tính quyết định vì nó đột phá hẳn tư duy cũ, cách làm cũ, về việc muốn lập các báo cáo phân tích phải làm Windows Form, phải xây dựng từ người lập trình ứng dụng, cung cấp báo cáo phải được xây dựng và quản lý bởi người quản trị và phải có Website, Windows Form hoặc Portal để cung cấp dịch vụ… Tất cả đều trở nên cổ điển với cách tư duy và thiết kế hệ thống mới… đó chính là BIS 2012.

Cách cấu hình máy chủ chuyển file Mozilla FTP trên windows server 2008


How to setup filezilla on windows server 2008. Start off by grabbing the server at http://filezilla-project.org/

image

Running the installer:

image

SGTM

image

Looks good. Continue reading below or comment with questions here.

image

Select where you want to install the server

image

I prefer to turn off the server admin interface:

image

That’s it. It’s done, now you just need to setup users, and allow port 20-21 through your firewall:

image

That’s it for the basic server setup. Now onto configuring server options:

image

Once setup, and you’ve configured your network properly, test it out. By default you’ll need to configure the windows firewall or you won’t be able to connect:

(000004)8/19/2010 10:57:37 AM – (not logged in) (208.8.241.6)> Connected, sending welcome message…
(000004)8/19/2010 10:57:37 AM – (not logged in) (208.8.241.6)> 220-FileZilla Server version 0.9.36 beta
(000004)8/19/2010 10:57:37 AM – (not logged in) (208.8.241.6)> 220-written by Tim Kosse (Tim.Kosse@gmx.de)
(000004)8/19/2010 10:57:37 AM – (not logged in) (208.8.241.6)> 220 Please visit http://sourceforge.net/projects/filezilla/
(000004)8/19/2010 10:57:37 AM – (not logged in) (208.8.241.6)> USER
(000004)8/19/2010 10:57:37 AM – (not logged in) (208.8.241.6)> 331 Password required for user
(000004)8/19/2010 10:57:37 AM – (not logged in) (208.8.241.6)> PASS **********
(000004)8/19/2010 10:57:37 AM – (208.8.241.6)> 230 Logged on
(000004)8/19/2010 10:57:37 AM – (208.8.241.6)> SYST
(000004)8/19/2010 10:57:37 AM – (208.8.241.6)> 215 UNIX emulated by FileZilla
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> FEAT
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> 211-Features:
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> MDTM
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> REST STREAM
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> SIZE
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> MLST type*;size*;modify*;
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> MLSD
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> AUTH SSL
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> AUTH TLS
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> UTF8
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> CLNT
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> MFMT
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> 211 End
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> PWD
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> 257 “/” is current directory.
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> TYPE I
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> 200 Type set to I
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> PASV
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> 227 Entering Passive Mode (192,168,1,101,226,100)
(000004)8/19/2010 10:57:38 AM – (208.8.241.6)> MLSD
(000004)8/19/2010 10:57:48 AM – (208.8.241.6)> 425 Can’t open data connection.

Go into the network and sharing center:

image

A look at how the firewall is configured:

image

Setting notifications will allow you to see if the firewall is blocking a program:

image

Go to advanced settings and create a new rule:

image

For a program:

image

Set the program you want to allow:

image

Allowed (if you want to go through secure configuration comment below)

image

For all networks:

image

Give it a name and your set:

image

Other then that you may want to set a server message welcome message, auto ban settings, etc:

image

Làm Thế nào để ẩn máy tính của mình trên mạng LAN


Máy tính của tôi có tên: ThinApp, mục đích để ẩn nó trong Network Icon ta sẽ làm theo những thao tác sau:
image
Bước 1: Chọn nút Start,chọn run search: “service”.

image

Bước 2: chọn mục dịch vụ “Function Discovery Resource Publication”:

image
Bước 3. Tiếp đến ta sẽ tùy chỉnh “Disabled” như sau:

image

Bước 4. Kiểm tra màn hình kết quả:

image

Cách sửa lỗi No remote Desktop License Server available on RD Session Host server 2012?


“No remote Desktop License Server available on RD Session Host server 2012 (event id 1130).”

Error in RDS 2012:

EventID: 1130
Source: TerminalServices-RemoteConnectionManager
The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer. Please contact the server administrator.”

Cách chữa theo các bước sau:

Bước 1. Xóa key license trial của RDSH cũ:

Hãy xoá tham số này trong Regedit  “REG_BINARY in”

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod

(hãy để phân quyền ở mức ownership để có thể xoá được key này.)

image

 

image

Sau đó khởi động lại tất cả Remote Desktop services.

Chú thích: bây giờ nếu bạn không thể xoá được hoặc chưa xoá được key này

Bạn cần thay lại quyền ownership cho Admin users và có full control để xoá key đó.

image

Bấm vào key cần ownership . Chọn menu Edit bấm Permissions> bấm tiếp Advanced và sau đó bấm Owner tab.

Nhóm chọn Replace owner on subcontainers and objects và bấm  new owner, và sau đó bấm OK.

Bước 2. Kiểm tra các cấu hình RDP Session Host Server Configuration:

image

image

 

image

Bước 3. Kiểm tra các RD Service, có thể restart service nếu không users kết nối:

image

Bước 4. Xóa thông báo TS theo lịch trình của Windows:

image

image

Bước 5. Kiểm tra xác nhận lại RDSH còn kết nối License:

image

Bước 6. Xóa tên máy chủ và tạo lại License mới thông qua kiểu Device:

image

Bước 7. Kiểm tra RemoteApp từ máy trạm và phát hiện lỗi remote:

image

Bước 8. Khởi động lại máy chủ RDSH:

Khởi động lại máy chủ và

Mở Server Manager lại kiểm tra các Services RDP

image

Nếu thấy lỗi services thì chọn nút phải chuột bật start /restart lại các services đó.

 

Chúc các bạn thành công !

%d bloggers like this: