mboost-dp1

unknown
- Forside
- ⟨
- Forum
- ⟨
- Nyheder
Fandt så lige ud af det på den spøjse måde, havde installeret og skulle til at patche... Hey hey SP2!
Så blev vores image gut lige ked af det, så skulle han lave alle 64bit images om, som han lige var blevet færdig med...
Nogle der ved hvordan man bliver holdt informeret om den slags på en hurtig og effektiv måde? - tror godt vores Sys ansvarlige kunne bruge den viden...
Så blev vores image gut lige ked af det, så skulle han lave alle 64bit images om, som han lige var blevet færdig med...
Nogle der ved hvordan man bliver holdt informeret om den slags på en hurtig og effektiv måde? - tror godt vores Sys ansvarlige kunne bruge den viden...
#7 selvfølgelig er der WGA-check.
Fedt med den SP2. Kæft der er mange opdatering i den! Check http://support.microsoft.com/kb/914962
Det er jo helt vildt.
Men EIH, de har stadig ikke fikset den fejl med serverside LDAP queries på CN... hulk ;(
Fedt med den SP2. Kæft der er mange opdatering i den! Check http://support.microsoft.com/kb/914962
Det er jo helt vildt.
Men EIH, de har stadig ikke fikset den fejl med serverside LDAP queries på CN... hulk ;(
Husk lige at teste den inden i ruller den ud :). Der er mange ting man skal tage højde for, blandt andet skal man afinstallere IE7 inden, hvis man har installeret den :]
Ja det var jo godt for dem, der bruger windows :)
Jeg holder min nu fortsat til min debian server :-)
[spoiler]
EDIT:
w00t hvorfor er mit indlæg blevet valgt som irrelevant?
[/spoiler]
Jeg holder min nu fortsat til min debian server :-)
[spoiler]
EDIT:
w00t hvorfor er mit indlæg blevet valgt som irrelevant?
[/spoiler]
Min RIS er holdt op med at virke efter opdatering til SP2.
Den fejlede også under installationen og sagde at jeg skulle være Administrator. Jeg er sjovt nok også admin på serveren.
Nu kan den bare ikke starte RIS servicen.
Den fejlede også under installationen og sagde at jeg skulle være Administrator. Jeg er sjovt nok også admin på serveren.
Nu kan den bare ikke starte RIS servicen.
#11
Release Notes for Microsoft Windows Server 2003 Service Pack 2
#12
Hvis man skal bruge IE7 via Citrix eller lign. teknologi, så bliver man jo nød til at installere det på en server :)
Og så den største grund til hvorfor man skal passe lidt på:
Hotfix Scan Tool for Windows Server 2003 Service Pack 2 Deployment - English
If you installed Internet Explorer 7 after installing Windows Server 2003 SP1, you must uninstall Internet Explorer 7 before you install Windows Server 2003 SP2.
Release Notes for Microsoft Windows Server 2003 Service Pack 2
#12
Hvis man skal bruge IE7 via Citrix eller lign. teknologi, så bliver man jo nød til at installere det på en server :)
Og så den største grund til hvorfor man skal passe lidt på:
You can use this tool to scan for hotfixes that will potentially regress after you install Microsoft Windows Server 2003 Service Pack 2 (SP2)
Hotfix Scan Tool for Windows Server 2003 Service Pack 2 Deployment - English
Lol hvor er det grimt: "har du en fuldt opdateret win2k3 server? TRIST, så skal du lige afinstallere dine updates, før du kører vores nye SP, som indeholder de updates du altså skal afinstallere først".
Lyder næsten som om det er nemmere at installere serveren forfra og derefter køre SP2. Bare ikke særligt effektivt :|
Blev ellers lige så glad, når jeg nu har planlagt nedetid snart alligevel.
Lyder næsten som om det er nemmere at installere serveren forfra og derefter køre SP2. Bare ikke særligt effektivt :|
Blev ellers lige så glad, når jeg nu har planlagt nedetid snart alligevel.
#17 -
If you are installing SP2 on a computer running SP1, to ensure that certain applications and components (such as Internet Explorer® 7 and Windows .NET Framework 2.0) function properly, install SP2 by using Update.exe. You can obtain Update.exe from the Microsoft Download Center (http://go.microsoft.com/fwlink/?LinkId=85446).
#16, #18
Some customers may inadvertently upgrade their Windows 2003 sp1 servers to sp2 without reading the relase notes, and if that server was a RIS server (remote installation services via pxe boot) then the customer will be in for an unwelcome surprise.
Amonsgt other things (release notes- http://technet2.microsoft.com/WindowsServer/en/lib... ) Service pack 2 upgrades your RIS server to act as a Windows Deployment Service, however in the process of doing so it effectively renders the 'old' Remote installation SERVICE obsolete (and this explains the cryptic errors below).
What does this mean to your customer ?
If they didn't know about it what they will see is all PXE boot attempts to their 'RIS' server will FAIL.
Symptoms include:-
Error on startup of the server immediately (and after every reboot) after installing Service Pack 2, stating
'a service failed to start, please check the event viewer for details'.
PXE boot failure on the client (no boot filename received error).
RIS service on the server fails to start with the following error if you try to start it manually -
'Could not start Remote Installation Service on local computer.
Error 127: the specified procedure could not be found.'
Steps to alleviate the problem:-
Advise customers to open administrative tools and to click on 'services'. Scroll down to 'Windows Deployment Services server' service, it will NOT be started and it's state is set to 'manual'. Ask the customer to start the service (they may wish to set it's startup type to 'automatic'.
Now, the customer should be able to PXE boot their clients as normal to the RIS server and deploy images exactly as they did before.
Other things to note:-
The new service is actually very useful to your customer, because now they can deploy Vista images via this server, however as SP2 is forcing the change gently from RIS to Windows Deployment Services what you will see are three modes for the new service (shown below). So effectively if the customer upgrades a SP1 RIS server to SP2, then they will be able to use the Windows Deployment Services in legacy mode to retain compatability with RIS.
More info about this below:-
Windows Deployment Services
Starting with this version of Windows Server 2003 with SP2, Remote Installation Services is replaced by Windows Deployment Services. You can use Windows Deployment Services to set up new computers through a network-based installation without having to be physically present at each computer and without having to install directly from DVD media. For more information about Windows Deployment Services, see the Windows Deployment Services Update Step-by-Step Guide
Overview on technet > http://technet2.microsoft.com/WindowsVista/en/libr...
Initial server mode
The method of installation and subsequent configuration actions dictate the initial server mode as follows:
Task Procedure
To get to Legacy mode: 1. Install the RIS optional component on Windows Server 2003 with SP1.
2. Install the Windows Deployment Services update.
3. Run RISETUP and add an image.
To get to Mixed mode: 1. Install the RIS optional component on Windows Server 2003 with SP1.
2. Run RISETUP and add an image.
3. Install the Windows Deployment Services update.
4. Run WDSUTIL /initialize-server.
To get to Native mode: 1. Install the RIS optional component on Windows Server 2003 with SP1.
2. Install the Windows Deployment Services update.
3. Run WDSUTIL /initialize-server.
Some customers may inadvertently upgrade their Windows 2003 sp1 servers to sp2 without reading the relase notes, and if that server was a RIS server (remote installation services via pxe boot) then the customer will be in for an unwelcome surprise.
Amonsgt other things (release notes- http://technet2.microsoft.com/WindowsServer/en/lib... ) Service pack 2 upgrades your RIS server to act as a Windows Deployment Service, however in the process of doing so it effectively renders the 'old' Remote installation SERVICE obsolete (and this explains the cryptic errors below).
What does this mean to your customer ?
If they didn't know about it what they will see is all PXE boot attempts to their 'RIS' server will FAIL.
Symptoms include:-
Error on startup of the server immediately (and after every reboot) after installing Service Pack 2, stating
'a service failed to start, please check the event viewer for details'.
PXE boot failure on the client (no boot filename received error).
RIS service on the server fails to start with the following error if you try to start it manually -
'Could not start Remote Installation Service on local computer.
Error 127: the specified procedure could not be found.'
Steps to alleviate the problem:-
Advise customers to open administrative tools and to click on 'services'. Scroll down to 'Windows Deployment Services server' service, it will NOT be started and it's state is set to 'manual'. Ask the customer to start the service (they may wish to set it's startup type to 'automatic'.
Now, the customer should be able to PXE boot their clients as normal to the RIS server and deploy images exactly as they did before.
Other things to note:-
The new service is actually very useful to your customer, because now they can deploy Vista images via this server, however as SP2 is forcing the change gently from RIS to Windows Deployment Services what you will see are three modes for the new service (shown below). So effectively if the customer upgrades a SP1 RIS server to SP2, then they will be able to use the Windows Deployment Services in legacy mode to retain compatability with RIS.
More info about this below:-
Windows Deployment Services
Starting with this version of Windows Server 2003 with SP2, Remote Installation Services is replaced by Windows Deployment Services. You can use Windows Deployment Services to set up new computers through a network-based installation without having to be physically present at each computer and without having to install directly from DVD media. For more information about Windows Deployment Services, see the Windows Deployment Services Update Step-by-Step Guide
Overview on technet > http://technet2.microsoft.com/WindowsVista/en/libr...
Initial server mode
The method of installation and subsequent configuration actions dictate the initial server mode as follows:
Task Procedure
To get to Legacy mode: 1. Install the RIS optional component on Windows Server 2003 with SP1.
2. Install the Windows Deployment Services update.
3. Run RISETUP and add an image.
To get to Mixed mode: 1. Install the RIS optional component on Windows Server 2003 with SP1.
2. Run RISETUP and add an image.
3. Install the Windows Deployment Services update.
4. Run WDSUTIL /initialize-server.
To get to Native mode: 1. Install the RIS optional component on Windows Server 2003 with SP1.
2. Install the Windows Deployment Services update.
3. Run WDSUTIL /initialize-server.
#3
Jo tak, Technet er fantastisk, hvis man kan lide cyklisk dokumentation, og iøvrigt hader sig selv. Technet er om muligt den værste informationskilde jeg nogensinde har oplevet, det eneste gode jeg har at sige om den, er at den er konsistent og ekstensiv.
Jo tak, Technet er fantastisk, hvis man kan lide cyklisk dokumentation, og iøvrigt hader sig selv. Technet er om muligt den værste informationskilde jeg nogensinde har oplevet, det eneste gode jeg har at sige om den, er at den er konsistent og ekstensiv.
Opret dig som bruger i dag
Det er gratis, og du binder dig ikke til noget.
Når du er oprettet som bruger, får du adgang til en lang række af sidens andre muligheder, såsom at udforme siden efter eget ønske og deltage i diskussionerne.