Jump to content

Fencer128

Member
  • Posts

    423
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by Fencer128

  1. Hi, I would manually delete the exisiting AD account for the machine and then try again. You can have problems with the existing account having been created by a user that has different privileges to the one currntly trying to add the account. So long as inheritence is enabled, joining a PC to the domain should simply require the permissions you have currently set up. Good luck, Andy
  2. Hi Rob, I hope it all works out for you. Is it your last day because you're leaving for pastures new (or just a holiday?) Good luck whichever it is Cheers, Andy
  3. That's because you haven't yet delegated that permission to the Installers group (see below) To do this, open up AD users and computers, right-click the domain at the top of the tree, select "Delegate Control" and follow the wizard to assign the permission to the correct group. Be warned to make sure you choose carefully as there isn't an un-delegate control wizard! Good luck, Andy
  4. Hi, If you've followed the instructions and used the latest DP Base with the latest DP MassStorage, then I suspect that the problem might be Windows 2000. Although some of the drivers may work with 2k, the packs were assembled with XP in mind. It could be that some of the files just aren't compatible. Can you try your method with a copy of XP to verify? Cheers, Andy
  5. Hi, Have you given the "Installers" security group the following specific permissions for the "Computers" container? "Create computer objects" "Delete computer objects" Also, have you delegated the group control to join computers to the domain? If so then comment out the following lines in your SIF file: DomainAdmin=risman DomainAdminPassword=xxxxxxxxxxxx This would then match your setup with ours, which does not have your problem. Sorry for all the questions, but I'm a bit lost with this one. Maybe the Sausage Eater or RogueSpear can shed a bit of light and clarity Cheers, Andy
  6. Hi, Just a thought (again ) Try adding this under [identification] in your SIF file: DoOldStyleDomainJoin = Yes Cheers, Andy
  7. Hi, Couple of thoughts: 1. Are you relying on RIS joining the PC to the domain at the end of the build, or are you running a post-installation script? 2. When you pass the %MACHINENEAME% variable through your RIS menu file, are you *just* passing the variable or are you also performing a server-side action? e.g: <META SERVER ACTION="CHECKGUID X8664 DUPCUST"> 3. Are both computer accounts being (attempted to) created within the same location in the AD schema? Cheers, Andy
  8. Hi, Can you try with a completely non-nlited CD, just to be absolutely sure of your diagnosis? Cheers, Andy
  9. @bluescreens Well spotted It appears to fix the parsing of the [Manufacturer] section of the INF files so that tweaking is no longer required. However, I'm using SP1, and according to MS (I just rang them), as you suggest, the hotfix is rolled in. It's been a while since I tried non-modified INFs so I may try at some point to see if the issue is resolved. Thanks again, Andy PS - The hotfix wouldn't have fixed the problem with the above network card and the Intel 10.2 drivers - I think it went deeper than the [Manufacturer] section as it was correctly formatted for RIS and we're using SP1.
  10. If you turn off the AERO GUI then I believe that's what you're left with. It may even be that the AERO GUI can be left out of the build, like a component in WinXP today, and not even be present on the HD, by the time Vista goes gold. Andy
  11. Hi, I use Symantec AV CE 10 and I don't get any virus warnings. It most likely sounds like a false-positive to me. EDIT: It seems from reading google groups that some malware uses this file as part of their installer. However, that doesn't mean that the file itself is malicious. In other words, unless other virus signatures are found then it appears to be a false-positive. Cheers, Andy
  12. Hi, Last thing Changed included Intel drivers to RIS specific versions now that they are available. Cheers, Andy
  13. Hi, Just thought I'd mention Sunbelt Counterspy Enterprise here - especially as it has good facilities for business use (e.g. reporting, push installation, remote console, etc). Also, for the time being it shares Microsoft's Defender's signature database. We've trialled it here and it's looking very good in terms of both price and features as compared to the competition. Cheers, Andy
  14. Hi Bashrat, New Realtek HDA drivers are out. You can download them from here: http://www.realtek.com.tw/downloads/dlhd-2...1&Software=True The usual "customisation" fixes, plus one for a crash with Adobe Premiere Pro 1.5 Cheers, Andy
  15. Hi Everyone, I've just released a new version of RISult. Some fairly big changes in this one : Upshot of all of this is that you now no longer need to manually run BTS_DriverPacks_BASE_Vxxx.exe everytime a new version is released or you want to change your driver pack collection. Just drop the new exe in one folder and/or the DPs in another and re-run RISult . Also, the whole file structure is now included within RISult.zip. Just extract to the root of C: and copy your files into the appropriate folders. I've also followed RogueSpears' lead and included text-mode drivers for Broadcom, Intel, Marvell and Realtek so that you can use RIS with these NICs (files are automatically added to your image). I've added a "btscustom.cmd" that you can choose to use (it doesn't run by default). Currently it alters BTS files so that ATI's CCC applet (the one that requires .NET FW 1.1) doesn't install. By request I've included a "Cleanup.cmd" that runs at first logon and deletes any TEMP remnants (such as the "D" folder) that are sometimes present due to BTS processes. Documentation and file names have been updated. Please be sure to re-read them before running RISult. Thanks especially go out to djbe for allowing me to include Fedit.exe with this version. Have Fun Andy PS - There will be a bit of a feature freeze from this point on. Bug fixes only, as I'm currently re-writing RISult to use VB and have a GUI interface.
  16. Hi, Yes DP_MassStorage, in conjunction with DP_BASE, is designed to add drivers for text-mode as well as Windows. Cheers, Andy
  17. What happens when you use the latest DP Base? Andy
  18. Hi, Sorry I don't know of any such groups (except maybe Google groups). Other than the options already mentioned - I think you may be stuck. Obviously Shuttle doesn't seriously target the enterprise market or they would test features such as RIS before they ship the product. Good luck! Andy
  19. Hi, You presume correctly - it is the local admin account. I don't know about logging on with other credentials as I've never had to do it I suspect that instead of using the SIF file in this instance, you will have to alter the registry to create the credentials you require and force the auto logon there. Remember though, it may mean that the domain credentials are visible to anyone who can access your RIS source files. Cheers, Andy
  20. Hi Chiners, I haven't made any changes to the part concerned with cleanups. I figured that the only way of doing this is to include a cleanup.cmd with the RISult.zip file and add a line to the code to add the following to ristndrd.sif: [GUIRunOnce] command11 = cleanup.cmd Where cleanup.cmd contains: @echo off TITLE Unattended Windows XP Service Pack 2 Setup echo Finalising installation and cleaning up hard disk del "%systemdrive%\temp\BTS_DPs_cleanup.cmd" /q rd "%systemdrive%\D" /s /q shutdown -r -t 60 -c "Computer will now reboot to complete installation" For the last while I've thought that it should be down to Bashrat to deal with this, and that the C++ version of the DP base may indeed do this. In the meantime I suggest you keep using cleanup.cmd. If I have time soon I will possibly add it to the pack in the way described above. Cheers, Andy PS - Does anyone else think that cleanup.cmd should be included?
  21. Hi, Out of impatience I've tried RIS with the PROSet 10.3 drivers - as is (i.e. I've not waited for any further release of a RIS specific version). EDIT: RIS specific drivers have now been released. They have been tested and work fine. The result is that on any 10/100 or gigabit system I've tried, inc. the D945GTP platform, everything has worked. I can thoroughly reccommend an upgrade to 10.3 if you are experiencing any issues with Intel NICs and RIS. Cheers, Andy ps - Only big chnage I noticed was to the file set for 10 Gigabit cards. They've changed some names and added another sys file. I don't have the hardware available to test this on at the moment, but if anyone knows anything about whether these latest drivers work with this hardware under RIS I'd be glad to know.
  22. Hi, The problem is the new Dell drivers. The workaround post above just replaces those drivers with the previous version. Hence, it will work for all methods. Cheers, Andy
  23. Hi, Presuming your RIS server is fine, it just sounds as if either the NIC hardware or firmware on the Shuttle is sub-standard. I would try the following: 1. Reflash the Shuttle's BIOS with the latest firmware in case of corruption. 2. If you're not already, try a Win 2k3 SP1 RIS server, instead of 2k. 3. If all else fails, try using a PCI NIC to build the box and then remove afterwards. Good luck, Andy P.S. I think you picked the wrong forum - check the sub-forum at the top of the page
×
×
  • Create New...