anyweb

I just ghosted my windows 2003 server (40GB) using ghost 8 using disc>disc to an 80GB target hdd, after completion, I then removed the 40gb and booted the 80GB hdd. At the login screen a popup error appeared stating:- Pressing OK and booting into directory services restore mode (press F8 at boot time and select it) boots Windows 2003 into safe mode, but as soon as you login, it logs out again. Very useful indeed (not). I guess I forgot to logon using the directory restore mode password, either way Microsoft recommends the following as a fix > http://support.microsoft.com/kb/258062 however, I found a much quicker and easier fix. Simply power off, insert the original hdd and boot up Ghost. In ghost options make sure to select the following option '-ID' copy entire disk including unpartitioned space' (image disk). I selected that option and ghosted disc>disc again, this time when all was done I could boot no problem into Windows 2003 with my new bigger hdd, and I now had a new unpartitioned 40gb of free space, marvellous. I chose to format that as another primary partition and will proceed to free up space on the other 3 partitions by moving data to the new partition. cheers anyweb

via osnews.com

more info > http://www.betanews.com/article/Microsoft_...blic/1186593846 via osnews.com

more info > http://www.windowsitpro.com/windowspaulthu...rott_96671.html

https://support.microsoft.com/contactus2/em...0&WS=hotfix if the above link doesn't work then try this one instead

if you want to change how RIS names your computers during an install, click on Active Directory Users and Computers, select Domain Controllers, highlight your RIS server and right click it, choose 'properties'. Click on the 'Remote Install' tab, then 'Advanced Settings'. In Advanced settings you can click on the drop down menu and select Custom and customize it to your fancy, then click apply and restart the RIS service. Please note this is for New Clients, so if you want it implemented on existing machines then you have to do two things, delete their current computer name from AD then do a new RIS install on each one indivually. Test it by RIS installing a new computer. screenshots below cheers anyweb

replace WINNT with WINDOWS (or whatever you called the windows directory) above, otherwise you'll get an error message. Restart the SQL service after making any changes. cheers anyweb

more info > http://news.com.com/8301-10784_3-9744971-7.html via osnews.com

can't connect to your SQL 2005 server ? check the tcp/ip options sql 2005 express edition that is secure out of the box. In sql 2005, the tcp/ip stack is disabled and remote connections are not allowed. Thats by default. So you first have to configure the sql 2005 express edition correctly, and take it from there. Try bringing up the SQL server configuration tool. You don't have the icon, so run C:\WINNT\system32\mmc.exe /32 "C:\WINNT\system32\SQLServerManager.msc" Select the client protocols option and enable TCP/IP

more info > http://arstechnica.com/news.ars/post/20070...008-launch.html via osnews.com

If you have installed and setup BDD 2007 you can try out the functionality contained within BDD 2007 to support Lite Touch scenarios. Their are four high level steps to describe the Lite Touch process. 1. Deploy the LTI (lite touch installation) infrastructure:- Several server roles are required to support the lite touch deployment process. These server roles may include the following:- * Build server - The source for customer deployment images, including out-of-box drivers, service packs and language packs. * Data Server - Used to store machine backups and User State Migration data (USMT) * Application installation server - Used to store the source files for core and supplemental application installations. * Microsoft Windows Deployment Services (WDS) server - The WDS server stores both boot and installation images for deployment and provides support for bare metal installations. This role is optional, if you prefer to use Windows Preinstallation Environment you wil not need WDS servers. 2. Configure the LTI servers - Each server role requires the following specific configuration tasks to be completed: * Build server - when planning the requirments for the deployment server, consider the amount of space required for the images used for the deployment. * Data server - installing the data server is a simple process of creating a network folder share and folder structures. * Application installation server - Creating the application installation server role involves the creation of another series of folders and network shares. * WDS server - This service was previously called the Remote Installation Service (RIS). WDS runs on Microsoft Windows Server 2003. In windows server 2003 service pack 1, it is delivered as an update through either the WAIK or Windows Server 2003 R2 (or via service pack 2 upgrade for Windows 2003 Server). It is available as a native server role in the latest version of Windows Server 2003. 3. Create the Windows PE and Windows Vista images - after the LTI infrastructure is in place, you can then use the deployment workbench to manage the images to be deployed. 4. Deploy the operating system images to the client computers - deploying the operating system to a client computer is a matter of having a user with administrative rights run the deployment wizard.

more info > http://blogs.zdnet.com/microsoft/?p=543 via osnews.com

more info > http://osnews.com/story.php/17995/Microsof...erface-Computer source > http://news.bbc.co.uk/1/hi/business/6703249.stm the video > http://crave.cnet.com/8301-1_105-9723647-1...l?tag=cnetfd.mt

more info > http://www.eweek.com/article2/0,1895,2130424,00.asp via osnews.com

more info > http://apcmag.com/6121/windows_server_gets...ta_version_itis via osnews.com

via osnews.com

I use AVG free, its quick, quiet and does the job and is Vista compatible. get it from here > http://free.grisoft.com/freeweb.php/doc/2/ cheers anyweb

more info > http://www.nynaeve.net/?p=121 via osnews.com

after completing a successful RIPREP on a Intel SOLO processor laptop I then decided to PXE boot the machine and RIPREP the image back on to it, however after logging in to the RIS server I could NOT see the RIPREP image that I had just done, after soom googling (ok, lots) I found out that the HalName=halmacpi.dll line in RIPREP.SIF file was causing the image to not be listed. The suggested fix was to delete that line altogether, so I did, saved the file and rebooted. This time it DID list the image but when I chose to use that image shortly afterwords the file copying stopped and I got the following error So, next I change the HalName=halmacpi.dll line to HalName=halaacpi.dll to see if that would alleviate the problem, it didnät (yet another error). After some more googling I found out that RIPREP relies on two files initially to decide what hal to use in setup, they are located in D:\RemoteInstall\Setup\English\Images\NEWIMAGE\i386\Mirror1 http://www.microsoft.com/technet/prodtechn...x.mspx?mfr=true IMirror.dat and BootCode.dat I opened IMirror.dat with notepad and saw that in there it referred to M u l t i p r o c e s s o r F r e e A C P I 1 . 0 - A P I C p l a t f o r m M P \ M i r r o r 1 \ U s e r D a t a \ D e v i c e \ H a r d d i s k 0 \ P a r t i t i o n 2 m u l t i ( 0 ) d i s k ( 0 ) r d i s k ( 0 ) p a r t i t i o n ( 2 ) I tried to manually edit this to read U n i p r o c e s s o r F r e e A C P I 1 . 0 - A P I C p l a t f o r m U P \ M i r r but that didnt work either. I knew there were some older machines on this RIS server that most likely were single cpu machines, so I copied the IMirror.dat from one of those machines and replaced my one, I then started PXE boot to the riprep server again, and this time it WORKED, this is not a supported hack by any means but it worked for me, We also used a freeware utility to edit the file by hand (WINHEX 3.x) and manually changed the MULTI to UNI but it didnät work (yet). cheers anyweb

error: could not drop object 'dbo.Devices' becuase it is referenced by a FOREIGN KEY constraint. For assistance, contact your SQL administrator or refer to the "Troubleshooting ACT Database Setup" topic in the online help system. screenshot of error below.

The Windows Vista Application Compatibility Toolkit (ACT 5.0) was created in part to address customers needs to assess whether there applications will work in Windows Vista. The following areas of Windows Vista are likely to cause areas of concern when considering Application Compatibility:- User Account Control (UAC) Windows Resource Protection (WRP) Internet Explorer 7 Protected Mode Windows Vista 64-bit Windows Filtering Platform Operating System version change Depreciations/GINA/Session 0 (high impact/low frequency) Where can I get this toolkit ? You can download the Windows Vista Application Compatibility toolkit from Microsoft's download centre. Part 1 - Installing the Application Compatibility Toolkit 5.0 In addition to the MSI download above, you should download the ACT 5.0 Product evaluation Guide and the ACT 5.0 readme. If you don't have the Windows installer 3.1 installed, you will be prompted to install it prior to installing the toolkit. The ACT 5.0 toolkit can be installed on the below operating systems: You will need a SQL database installed also, In addition to the above, the toolkit requires the .net framework version 1.1 installed. Once the toolkit is installed (at the end of the installer) you are given the option to watch a short video/demo about the product. You can view that video here. To configure settings so that the ACT Log Processing Service can access the SQL database, provide the Computer Account (not the user account) with both Read and Write permissions on the SQL database. Note: It is the Computer Account, not the User account that uploads the log file. On your SQL server, locate the ACT database, expand it so that you can see Security, Users, then Grant the ACT computer account db_owner permissions to that DB. To launch the toolkit, click on Start/Programs/Microsoft Application Compatibility Toolkit 5.0/Application Compatibility Manager It'll take a few minutes to start and then present you with the three things it is about to do:- * configure an ACT database (sql server) * configure ACT log share * configure ACT log processing service account Next you will be given the choice of configuring it for * Enterprise configuration (configure this computer to view log files and reports) or * View and manage reports only. Obviously if you want to test the tool, choose the first option above. In the next screen, you are given the options to choose your SQL server, and database name (or to create a new database). If you get a database creation error similar to this one then reinstall SQL server express edition and do NOT choose the 'default' setup (remove the tick from 'hide advanced options' ) and when you get to the name of the server, make sure it's not selected on the 'default' option, but rather 'named'. Once the database is created it will prompt you to create a log file and it will automatically share this folder to the domain, next it will prompt you to configure your ACT log processing service account, I went with the default setting of 'local system'. If all goes well you will be presented with a Congratulations screen and you can click on 'finish' to start the application. Once the gui presents itself, we are nearly ready to test. Verify that the ACT log processing service is running After the ACT 5 has been installed, you need to make sure that the ACT5 log processing service is running. The service continually scans the directory defined in the configuration settings looking for unprocessed log files. To verify that it is running, click on start/run and type 'services.msc'. In the list of services, check the ACT Log Processing service and verify that it's reporting 'started for status, and Automatic for startup type. IF it is not running, manually start it. Ok, now we are ready to Collect data. Part 2 - Collect an application Inventory. If it isn't running already, click on Start|All Programs|Microsoft Application Compatibility toolkit 5.0|Application Compatibility Manager. Click on 'Collect' in the lower left end of the GUI. From the file menu, select New to create an ACT DCP package. Type ACT_001 in the Package Name text box. Verify that 'Deploying a new operating system or service pack' is selected under the 'Evaluate compatibility when' choice. Set the duration to 60 minutes under the 'When to monitor application usage' choice. This should be enough time for the agent to collect information and monitor our use of IE and other installed applications. In a production environment, you'd typically want to set this for at least 3-5 days to capture sufficient detail. Click on the 'Advanced' tab, and make sure the following are selected. Internet Explorer Compatibility Evaluator (IECE) Inventory collector User Account Control Compatibility Evaluator (UACCE) Windows Vista compatibility Evaluators (detects issues related to GINA, Session 0, and depreciated components usage in applications on Windows Vista). Click 'ok'. Then from the file menu, select 'save and create package' and save it in c:\act_packages (which if you havn't already created and shared, then please do so). ACT packages can be deployed via login scripts, email, AT commands or software distribution solutions like SMS server 2003. Once you have done the above, verify that you can actually write to the ACT_log directory from another pc, otherwise the reports will not get written. To verify simply create a new txt file in that directory from the intended test machine, if it fails with 'access denied' then right click on the 'ACT_log' share, and click on properties/sharing/Permissions. In addition check the Security tab and make a note/adjust the settings for 'everyone'. Give 'Everyone' the access you require for this test. Failure to do so may leave you with an error similar to this one on the event viewer of the test system that you run the package on. Deploying an ACT 5 agent. In production, you may need to deploy multiple agent packages on your clients, but do keep in mind that only one package can be installed and running at a time on a client. Find an XP client computer to do the test deployment on and navigate to the act_packages share in the network. \\servername\act_packages\ACT_001 (Win32 Cabinet Self Extractor file) The servername above is the computer that we installed the ACT on in Part 1 above. To verify that the package installed you can check 'add/remove programs' in Control panel and you should see the Microsoft Application Compatibility Toolkit Data Collector 5.0' listed. If you now start IE7 on the XP client computer, you will see a small pop-up telling you that the IE compatibility evaluation logging is turned on. Now that you've got it running, start using IE7 and peruse some sites that will send a popup in IE7. We are doing this to which we will analyse later. Part 3 - Organizing your inventory. The Microsoft Application Toolkit 5.0 will produce an application portfolio which we can sync with information from the ACT online community exchange. Part 4 - Reports To create a report that would display the updates that may cause compatibility issues, you would use one of the following standardized reports: Update Impact Reports - Applications, or Update Impact Reports - Updates. Either of these reports will display information regarding the updates that could cause compatibility issues and the applications that are affected by them. The information for these two reports is gathered by the Update Compatibility Evaluator (UCE) tool included with ACT 5.0. You can see a very good walkthrough of ACT 5 here

What is WDS ? Windows Deployment Services (Windows DS or WDS) is the updated/redesigned version of RIS (Remote Installation Services). It replaces Remote Installation Services (RIS) and is available as an add-on for Windows 2003 SP1 through the WAIK (Windows Automated Installation Kit). How can I install it in Server 2003 SP1 ? If you want to install it in Windows Server 2003 Sp1 then use the included EXE file on the WAIK DVD (or mount the ISO) The WDS installation file (for Windows Server 2003 SP1) is available in two versions windows-deployment-services-update-x86.exe and windows-deployment-services-update-amd64.exe choose whichever version is appropriate to your release. How can I install it in Server 2003 SP2 ? Windows Deployment Services is included in Windows Server 2003 SP2. To install WDS in Server 2003 SP2, go into control panel, add remove programs and click on Add Remove Windows Components Scroll down to the bottom, select Windows Deployment Services by placing a checkmark and click Next. If it prompts for the CD enter it and click next, click Finish when done. You will be prompted to restart the server, so click on Yes to reboot. How can I install it in Server 2008 ? WDS is a role in Windows Server 2008, you just have to add it and configure it. What can I do with WDS ? With WDS, you can install Windows Vista, Windows Server 2008, Windows XP, Windows Server 2003, and Windows 2000 images. In addition, the WIM images are sysprepped. Windows Deployment Services uses WinPE as the boot environment on the target PC, WinPE can be customised and WinPE is deployed as a compressed WIM image with RAMDISK boot support. WDS provides a new set of management tools for common server tasks, for example there is the UI tool itself which is a MMC console application, and there is a command line tool which is scriptable (wdsutil), both of these tools use the MGMT API layer. WDS can be remotely administered and the management console can handle multiple WDS servers. WDS offers a capture utility, a GUI utility to capture images into WIM format, this is a light version of imageX/capture functionality plus a UI. WDS features an Active Directory users and computers extension and an updated version of RISETUP (Windows Server 2003 only). Windows Server 2008 will offer multicast capabilites with WDS. How does WDS work ? There are three modes of operation for WDS. Legacy In Legacy mode (Windows Server 2003), the WDS server uses WDS binaries but gives RIS functionality, it still uses the 'dos' based oschooser and RISetup and RIPrep funtionality. Management is via RIS utilities. Mixed In mixed mode (Windows Server 2003), WDS offers both OSChooser and WinPE booting, plus RISetup, RIPrep and WIM functionality. Management of RIS is via the RIS utilities, and management of WDS via the WDS mmc console or command line utility (wdsutil). The mode requires that RIS has been pre-configured on the Windows 2003 server. Native In native mode (both Windows Server 2003 and Windows Server 2008), there is NO RIS functionality, you will only have access to WinPE or WIM images. Management of WDS is via the WDS mmc console or via command line, and Native mode is the only option in Windows Server 2008. If you would like to configure WDS via the MMC gui then please read this post. Troubleshooting WDS IF you get access denied errors when configuring WDS via the command prompt:- see below the access denied error above occurred immediatly after trying to create a folder called images on the WDS SHARE (REMINST). So I checked the properties of the share and gave EVERYONE full acess. Now when I tried wdsutil it worked, see below. So to recap:- to initialize your WDS server you could do it via the gui wizard or via command line by issuing wdsutil /verbose /progress /initialize-server /reminst:"e:\RemoteInstall" the e:\Remoteinstall path should be changed to the path of your RemoteInstall folder. In addition once done make sure to open up the WDS MMC gui at least once. You can use WDS to capture 4 types of images * boot * capture * install * discover A discover image is used when you do not have access to a PXE server. how can I CAPTURE an Image using WDS ? To capture an image using WDS do as follows how can I DEPLOY an Image using WDS ? To deploy an image using WDS do as follows:

below are the steps from start to finish to get the Windows Vista Hardware Assessment tool to complete it's reports. 1. Start the wizard. 2. Enter new Database name or use existing. 3. Select the Actions to perform. 4. Specify the Windows Workgroups and domains to include in the inventory (no screenshot) 5. Enter the username/pass for Active Directory inventory 6. What local account should I use ? 7. Show summary of performed selections 8. Collecting and Preparing data (this is where it goes to actually find other computers and see if they are Vista ready) 9. Report is ready ! 10. All done, time to view the reports

try this open a command prompt and type slmgr -xpr you'll get a popup window (eventually) telling you that you are permanently activated (lucky you) or how many days left till activation. cheers anyweb

ImageX is a tool which is part of the Windows Automated Installation Kit (WAIK) and can be used to mount and modify the content of Windows Image (WIM) files. To use imageX you could create a WinPE cdrom or usb key with the imagex tool on it, then boot a system that you wish to create an image of or copy an image to, for example (to copy the contents of a machine to a Windows Image (WIM) file) do as follows:- e:\imagex.exe /compress fast /capture x:/vistaultimate.wim "Windows Vista Ultimate Edition" /verify where e:\ is the usb Key/CD with WinPE on it, and x:/ is your network share (or external hdd). To image another machine with this captured image do as follows:- Boot from the cd/usb key with WinPE and the imagex.exe tool on it, then e:\imagex.exe /apply x:/vistaultimate.wim 1 c: To edit a WIM file using imageX see this post. cheers anyweb