Few days suffering from this error : "Wndows connot connect to event notification service"
to resolve that :
1. Reboot your computer into Safe Mode (with Networking).
2. Open regedit and delete the following two keys and all their subs:
HKLM/System/CurrentControlSet/Services/Winsock
HKLM/System/CurrentControlSet/Services/Winsock2
3. Reboot your computer again and let it start up normally (non-safe mode).
voilà!
Affichage des articles dont le libellé est Windows. Afficher tous les articles
Affichage des articles dont le libellé est Windows. Afficher tous les articles
mardi, novembre 26, 2013
mardi, juin 23, 2009
Windows Deployement Service Episode1 : Error on client if changing server Name
I have a small poblem with Windows deployment service. At the first time, I installed it on server called Server1 with SCCM, SQL, WSUS…..since I need to put it on a separated server, so I decide to deploy it on a server called Server2. nice !
On Server2, Deployement workbench is installed with all necessary files, and WDT. Distribution files need to be modified :
- Bootstrap.ini & CustomSettings.ini
- Unattend.xml
- Deploy.xml
Next, configuring option 60 on DHCP to point on Server2, and allowing clientsanswer, and authorize server (command prompt wdsutil). Then updating deployment points.
At this point we can see that WDS is configured properly, but when I test the installation of a laptop, it detect the network pxe image, but at the beginning of installation after "wpeinit", the installer is asking for Server1 share, I am sure that all files (Bootstrap.ini, CustomSettings.ini, Unattend.xml and Deploy.xml) are configured properly, and images updated.

The problem is stupid : I have used the same laptop to test installation of the image from Server1 before, now the laptop boot, load files, and maybe it keep some files on HDD from previous installation, so Microsoft has no plans to replace the files loaded at boot time for a new installation :p
If you need to use the same box to test the installation after changing the server name, you should format the HDD before !
On Server2, Deployement workbench is installed with all necessary files, and WDT. Distribution files need to be modified :
- Bootstrap.ini & CustomSettings.ini
- Unattend.xml
- Deploy.xml
Next, configuring option 60 on DHCP to point on Server2, and allowing clientsanswer, and authorize server (command prompt wdsutil). Then updating deployment points.
At this point we can see that WDS is configured properly, but when I test the installation of a laptop, it detect the network pxe image, but at the beginning of installation after "wpeinit", the installer is asking for Server1 share, I am sure that all files (Bootstrap.ini, CustomSettings.ini, Unattend.xml and Deploy.xml) are configured properly, and images updated.

The problem is stupid : I have used the same laptop to test installation of the image from Server1 before, now the laptop boot, load files, and maybe it keep some files on HDD from previous installation, so Microsoft has no plans to replace the files loaded at boot time for a new installation :p
If you need to use the same box to test the installation after changing the server name, you should format the HDD before !
mercredi, avril 08, 2009
dimanche, septembre 07, 2008
Windows server limits!
turning around blogs, I found this awesome post Pushing the Limits of Windows: Physical Memory, but my fist surprise was the feeling of seeing this image that i will never see in my real work world :-) , a server with 2TB of memory and 64 cores !!!
jeudi, avril 27, 2006
Windows server 2003 R2
today i received my MSDN pack with especialy windows 2003 R2. The following table lists features added for Microsoft Windows Server 2003 R2.
Active Directory Federation Services
Active Directory Federation Service (ADFS) enables Federated Identity and Access Management by securely sharing digital identity and entitlements rights across security and enterprise boundaries. ADFS provides a secure, reliable, scalable, and extensible identity federation solution.
Common Log File System
The Common Log File System (CLFS) API provides high-performance, general-purpose file log services that dedicated client applications can use and multiple clients can share to optimize log access.
Distributed File System Replication
Distributed File System Replication (DFSR) introduces a WMI provider that you can use to create tools for configuring and monitoring the Distributed File System Replication (DFSR) service.
Microsoft Management Console 3.0
The managed framework for Microsoft Management Console (MMC) version 3.0 provides a richer snap-in development experience than MMC 2.0. Snap-in development in MMC 3.0 offers a near-zero ramp-up time and facilitates the continuous incremental improvement of snap-in implementations.
Version detection
To determine whether the current operating system is Windows Server 2003 R2, use the GetSystemMetrics function with SM_SERVERR2.
Web Services for Management
The Web Services for Management (WS-Management) provides local and remote management of server hardware, especially Baseboard Management Controllers (BMC). It uses a standard SOAP-based, firewall-friendly protocol, and a Windows Management Instrumentation (WMI) provider to diagnose server hardware even when the operating system is not running. You can access both WMI and BMC data either from the WS-Management command-line tools or from scripts written with WS-Management scripting objects.
Active Directory Federation Services
Active Directory Federation Service (ADFS) enables Federated Identity and Access Management by securely sharing digital identity and entitlements rights across security and enterprise boundaries. ADFS provides a secure, reliable, scalable, and extensible identity federation solution.
Common Log File System
The Common Log File System (CLFS) API provides high-performance, general-purpose file log services that dedicated client applications can use and multiple clients can share to optimize log access.
Distributed File System Replication
Distributed File System Replication (DFSR) introduces a WMI provider that you can use to create tools for configuring and monitoring the Distributed File System Replication (DFSR) service.
Microsoft Management Console 3.0
The managed framework for Microsoft Management Console (MMC) version 3.0 provides a richer snap-in development experience than MMC 2.0. Snap-in development in MMC 3.0 offers a near-zero ramp-up time and facilitates the continuous incremental improvement of snap-in implementations.
Version detection
To determine whether the current operating system is Windows Server 2003 R2, use the GetSystemMetrics function with SM_SERVERR2.
Web Services for Management
The Web Services for Management (WS-Management) provides local and remote management of server hardware, especially Baseboard Management Controllers (BMC). It uses a standard SOAP-based, firewall-friendly protocol, and a Windows Management Instrumentation (WMI) provider to diagnose server hardware even when the operating system is not running. You can access both WMI and BMC data either from the WS-Management command-line tools or from scripts written with WS-Management scripting objects.
Inscription à :
Articles (Atom)