Showing posts with label server. Show all posts
Showing posts with label server. Show all posts
Sunday, August 28, 2016
dcpromo demote Win2k3 server Failed to configure the service NETLOGON as requested
dcpromo demote Win2k3 server Failed to configure the service NETLOGON as requested
Heres the full text of the error received:
the operation failed because:
Failed to configure the service NETLOGON as requested.
"The wait operation timed out"
and in the dcpromo.log is the following:
07/07 09:02:24 [INFO] Informed NETLOGON to deregister records
07/07 09:02:24 [INFO] Stopping service NETLOGON
07/07 09:04:24 [INFO] StopService on NETLOGON failed with 258
To fix:
Change the first DNS setting on your network card to point to your new DNS server, not the server you are currently demoting. Once you change the DNS setting to the new DNS server you will be able to demote the server without this issue.
Saturday, August 20, 2016
Configure an External Time Source in Windows Server 2008 R2
Configure an External Time Source in Windows Server 2008 R2
Configure an external time source
This computer is configured to hold the primary domain controller (PDC) emulator operations master role (also known as flexible single master operations or FSMO) in the forest root domain. This computer should not use itself as a time source. Configure an external time source as the authoritative time source for the forest, or configure a member domain controller as the time source peer. The configuration must be done manually. Perform the following procedure on the computer that is logging the event to be resolved.To perform this procedure, you must have membership in Domain Admins, or you must have been delegated the appropriate authority.
To configure a manual time source peer:
- Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- At the command prompt, type w32tm /config /manualpeerlist:server,0x8, /syncfromflags:manual /update, where server is the name of the time source that you want to configure, and then press ENTER. ((I recommend pool.ntp.org for an Internet source))
- Restart the Windows Time service. At the command prompt, type net stop w32time & net start w32time, and then press ENTER.
- Resynchronize the Windows Time service client with the time source peer. At the command prompt, type w32tm /resync, and then press ENTER.
To learn more about the Windows Time service and related tools, see Windows Time Service Tools and Settings (http://go.microsoft.com/fwlink/?LinkID=42984).
To verify that the Windows Time service is synchronizing correctly:
Verify
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.To verify that the Windows Time service is synchronizing correctly:
- Open a command prompt as an administrator. To open a command prompt as an administrator, click Start. In Start Search, type Command Prompt. At the top of the Start menu, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- At the command prompt, type W32TM /resync, and then press ENTER.
- At the command prompt, type W32TM /query /status, and then press ENTER. This command displays the status of the Windows Time service synchronization. The Last Successful Sync Time line of the output displays the date and time that you ran the W32TM /resync command in the previous step. Also, check the computer name that is shown as the Source. This should be the name of a domain controller (or an administrator-configured time server) in the same Active Directory domain as the local computer.
Friday, August 19, 2016
Exchange SP2 Install Error This Server Role Cant Be Installed Because the Following Roles
Exchange SP2 Install Error This Server Role Cant Be Installed Because the Following Roles
Mailbox role
Error: this server role cant be installed because the following roles arent current: AdminToolsRole MailboxRole
Heres the fix for it:
Open REGEDIT
1. HKLMSoftwareExchangeServerV14AdminToolsConfiguredVersion
Change ConfiguredVersion from 14.1.218.5 to 14.2.247.5
2. Repeat this process for the other keys labeled TRANSPORTROLE or MAILBOX role as needed. The different versions on those numbers are the source of the problem.
3. Restart server and then start Exchange 2010 SP2 setup again.
Good luck!
Thursday, August 11, 2016
Fix VSS Errors Windows XP and Server 2003
Fix VSS Errors Windows XP and Server 2003
Installing a backup device that uses a backup agent means the VSS writers have to be free of errors. You can fix this by opening a command prompt (administrator level if needed) and typing in "vssadmin list writers". This will run for a few seconds then list all of the writers on the system. They should all show as "stable and ready". If they are not, below are the steps you can take to fix this problem.
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftEventSystem{26c409cc-ae86-11d1-b616-00805fc79216}Subscriptions
3. On the Edit menu, click Delete, and then click Yes to confirm that you want to delete the subkey.
4. Exit Registry Editor.
5. Click Start, click Run, type services.msc, and then click OK.
6. Right-click the following services one at a time. For each service, click Restart:
- COM+ Event System
- COM+ System Application
- Microsoft Software Shadow Copy Provider
- Volume Shadow Copy
7. Click Start, click Run, type cmd, and then click OK.
8. At the command prompt, type vssadmin list writers, and then press ENTER.
9. If the VSS writers are now listed, close the Command Prompt window. You do not have to complete the remaining steps. If the VSS writers are not listed, type the following commands at the command prompt. Press ENTER after each command.
- cd /d %windir%system32
- net stop vss
- net stop swprv
- regsvr32 ole32.dll
- regsvr32 oleaut32.dll
- regsvr32 vss_ps.dll
- vssvc /register
- regsvr32 /i swprv.dll
- regsvr32 /i eventcls.dll
- regsvr32 es.dll
- regsvr32 stdprov.dll
- regsvr32 vssui.dll (does not work in Windows XP)
- regsvr32 msxml.dll
- regsvr32 msxml3.dll
- regsvr32 msxml4.dll
Note The last command may not run successfully.
10. At the command prompt, type vssadmin list writers, and then press ENTER.
11. Confirm that the VSS writers are now listed.
12. At the command prompt, type vssadmin list shadows and then press ENTER.
13. Confirm that there are no errors listed. On Windows XP you should see: No shadow copies present in the system.
14. Congratulations your machine should work again with any VSS compatible programs.
Saturday, August 6, 2016
ESP 05 ESP8266 Arduino Mega act as simple web server
ESP 05 ESP8266 Arduino Mega act as simple web server
Last post introduced ESP-05 (a mini ESP8266 board) with simple testing. This post show a very simple web server on Arduino Mega 2560 + ESP-05.
Basically, its same as the example of "Arduino + ESP8266 - Web Server (III) with firmware 00200.9.5(b1)", except the baud rate.
Mega_ESP05_Web.ino
/*
Arduino Mega 2560 + ESP-05(ESP8266)
ESP-05 running firmware:
AT version:0.40.0.0(Aug 8 2015 14:45:58)
SDK version:1.3.0
Ai-Thinker Technology Co.,Ltd.
Build:1.3.0.2 Sep 11 2015 11:48:04
Connection between Mega & ESP-05,
refer "Connect with Arduino Mega 2560 via Level Converter" in:
http://goo.gl/wtG89i
Mega + ESP_05 act as station, join WiFi AP of my phone.
Once server setup, you can visit the webpage in ESP-05
by visit the IP show in Serial Monitor, under the command:
AT+CIFSR
+CIFSR:STAIP,"192.168.43.15"
If always show "Module have no response.",
check your connection, or reset ESP-05 by power OFF and ON.
*/
#define ASCII_0 48
#define ESP8266 Serial3
//WiFi hotspot setting on my phone
String SSID = "ssid";
String PASSWORD = "password";
int LED = 13;
boolean FAIL_8266 = false;
String strHTML1 = "<!doctype html>
<html>
<head>
<title>arduino-er</title>
</head>
<body>
<H1>arduino-er.blogspot.com</H1>";
String strHTML2 = "</body>
</html>";
//String strHTML = "arduino-er.blogspot.com";
#define BUFFER_SIZE 128
char buffer[BUFFER_SIZE];
void setup() {
pinMode(LED, OUTPUT);
digitalWrite(LED, LOW);
delay(300);
digitalWrite(LED, HIGH);
delay(200);
digitalWrite(LED, LOW);
delay(300);
digitalWrite(LED, HIGH);
delay(200);
digitalWrite(LED, LOW);
do{
Serial.begin(115200);
ESP8266.begin(115200);
//Wait Serial Monitor to start
while(!Serial);
Serial.println("--- Start ---");
ESP8266.println("AT+RST");
delay(1000);
if(ESP8266.find("ready"))
{
Serial.println("Module is ready");
ESP8266.println("AT+GMR");
delay(1000);
clearESP8266SerialBuffer();
ESP8266.println("AT+CWMODE=1");
delay(2000);
//Quit existing AP, for demo
Serial.println("Quit AP");
ESP8266.println("AT+CWQAP");
delay(1000);
clearESP8266SerialBuffer();
if(cwJoinAP())
{
Serial.println("CWJAP Success");
FAIL_8266 = false;
delay(3000);
clearESP8266SerialBuffer();
//Get and display my IP
sendESP8266Cmdln("AT+CIFSR", 1000);
//Set multi connections
sendESP8266Cmdln("AT+CIPMUX=1", 1000);
//Setup web server on port 80
sendESP8266Cmdln("AT+CIPSERVER=1,80",1000);
Serial.println("Server setup finish");
}else{
Serial.println("CWJAP Fail");
delay(500);
FAIL_8266 = true;
}
}else{
Serial.println("Module have no response.");
delay(500);
FAIL_8266 = true;
}
}while(FAIL_8266);
digitalWrite(LED, HIGH);
//set timeout duration ESP8266.readBytesUntil
ESP8266.setTimeout(1000);
}
void loop(){
int connectionId;
if(ESP8266.readBytesUntil( , buffer, BUFFER_SIZE)>0)
{
Serial.println("Something received");
Serial.println(buffer);
if(strncmp(buffer, "+IPD,", 5)==0){
Serial.println("+IPD, found");
sscanf(buffer+5, "%d", &connectionId);
Serial.println("connectionId: " + String(connectionId));
delay(1000);
clearESP8266SerialBuffer();
sendHTTPResponse(connectionId, strHTML1);
sendHTTPResponse(connectionId, "<hr/>-END-<br/>");
sendHTTPResponse(connectionId, strHTML2);
//Close TCP/UDP
String cmdCIPCLOSE = "AT+CIPCLOSE=";
cmdCIPCLOSE += connectionId;
sendESP8266Cmdln(cmdCIPCLOSE, 1000);
}
}
}
void sendHTTPResponse(int id, String response)
{
String cmd = "AT+CIPSEND=";
cmd += id;
cmd += ",";
cmd += response.length();
Serial.println("--- AT+CIPSEND ---");
sendESP8266Cmdln(cmd, 1000);
Serial.println("--- data ---");
sendESP8266Data(response, 1000);
}
boolean waitOKfromESP8266(int timeout)
{
do{
Serial.println("wait OK...");
delay(1000);
if(ESP8266.find("OK"))
{
return true;
}
}while((timeout--)>0);
return false;
}
boolean cwJoinAP()
{
String cmd="AT+CWJAP="" + SSID + "","" + PASSWORD + """;
ESP8266.println(cmd);
return waitOKfromESP8266(10);
}
//Send command to ESP8266, assume OK, no error check
//wait some time and display respond
void sendESP8266Cmdln(String cmd, int waitTime)
{
ESP8266.println(cmd);
delay(waitTime);
clearESP8266SerialBuffer();
}
//Basically same as sendESP8266Cmdln()
//But call ESP8266.print() instead of call ESP8266.println()
void sendESP8266Data(String data, int waitTime)
{
//ESP8266.print(data);
ESP8266.print(data);
delay(waitTime);
clearESP8266SerialBuffer();
}
//Clear and display Serial Buffer for ESP8266
void clearESP8266SerialBuffer()
{
Serial.println("= clearESP8266SerialBuffer() =");
while (ESP8266.available() > 0) {
char a = ESP8266.read();
Serial.write(a);
}
Serial.println("==============================");
}
Download the file .
Monday, August 1, 2016
FOG server error host unreachable when trying to upload an image
FOG server error host unreachable when trying to upload an image
Tonight Im doing some imaging of HP tablets and upgrading them from Windows XP to Windows 7. This is a new FOG installation and I just ran into this error. Heres the fix:
No matter what you named the FOG server on your network, make sure you have a DNS entry on your DNS server that DHCP is pointing to and create an A record named "fogserver" minus the quotes of course.
Once you do that then restart the machine you want to push the image of to your FOG server. Problem solved and it will upload after that. On a 100M switch you can expect about 1.4 to 1.5G/min so the average new image runs about 20-25 minutes to upload. Obviously gig switches are much faster provided your backend can keep up.
Good luck.
Subscribe to:
Posts (Atom)