Jump to content

TheCrust

Members
 View Profile  See their activity

  • Posts

    303

  • Joined

 Content Type 

Everything posted by TheCrust

  1. TheCrust
    Where are you seeing the problem? Do your users see it, or do you see it when you're browsing a list of the folders in explorer when logged on as admin? We see the latter on our file servers. At first the initial reaction was more one of "what the chuff is going on here....?" when you see a long list of what looks like the same folder, but as you've already sussed out, it's a display thing only. From what I remember, its down to Vista giving folders more "cuddly" names without actually changing their filename on the disk - it stores the display name in the desktop.ini file in the root of the folder. Which is all well and good until you start going through the top-level folder storing user home drives looking for a specific one and find them all called "Documents". Helpful. Not. I read that it's down to the administrative account (or logged on user if you are using another one) having read access to all those desktop.ini files. The way around it that was being pitched in the document I saw is to deny administrative access to those desktop.ini files - this will prevent Explorer reading the files and displaying the folders using their Vista-based name and you will see the true folder name instead. The user, still having rights to it, sees the folder names as Vista wants to display them. Deleting the files might also work, but then there's the chance the next time the users use Vista-based machines that the files are recreated and you're right back to square one. Or you could do what we do - ignore it - and click in the breadcrumb trail at the top of the screen and enter the folder name in the path you're searching for: that will soon highlight the folder you want.
  2. TheCrust
    That's how we're backing up the R2 boxes at the moment - individual backup jobs dumping their files over to a NAS box - but I'd much rather be able to stick it onto the same tape as the rest and stick that in our offsite safe! Oh well, Arcserve backup here I come!
  3. TheCrust
    Does anyone know if its possible to buy just the 12.5 client agents for our R2 boxes and have them backup to our 12.0 media server? I know newer versions of the media server will support older clients, but what about older media servers supporting newer clients...? I am loathe to buy the new version of BackupExec just to support the move over to R2 and am seriously contemplating alternatives, but I'd much rather adapt our existing infrastructure to support the new servers if I can.
  4. TheCrust
    Out of interest, do you have any Vista or Windows 7 machines on the network too? We get this occasionally on our few remaining XP clients and the XP Embedded winterms - the perception is that it started once we moved over to a mainly Vista network some years ago.
  5. TheCrust
    This post is in relation to this thread, posted by my senior feeder school tech some time ago: http://www.edugeek.net/forums/networks/41382-drive-mapping-woes.html The workstations are all clean-build XP Service Pack 3, deployed from WDS and operating in a native Windows Server 2003 domain. As with all primary schools, there is the usual plethora of wonderfully reliable software installed (even workshark!) - but none of the usual crud bloatware that comes with PCs from new such as the inevitable free PDF utility, google desktop etc.. It seems the workstation service on these machines is terminating randomly - there are no entries in the system or application logs to indicate why the service is stopping, or an application that may be tripping it up. The service just.... .....stops. A reboot will bring it all back to life, but the fix isn't permanent and machines are having to be regularly restarted - not ideal in a classroom environment when all the teacher wants is for stuff to work as it should. Does anyone have any ideas? I have a feeling it's related to SP3 itself but can't put my finger on it and a quick google turns up nothing useful. Thanks in advance! Jim
  6. TheCrust
    Horses for courses really - either option works.
  7. TheCrust
    I didn't realise it could be done via Group Policy too - once I worked out a solution I stopped looking. The advantage of our MSI-based approach is that we can easily change the backgroundDefault image as we see fit - perhaps to promote in-school activities, events or simply to keep the kids interested. All the GPO approach seems to be able to do is turn it on or off - it's useful nonetheless!
  8. TheCrust
    You might want to check to see how your Windows 7 installation partitioned the disk when you did your original setup. We had the same problem with the RC during testing and then with the 7 Enterprise image we used after RTM. Initially I just put it down to the new OS being beta, then my lack of understanding of it but when I looked at the installation in more detail, I noticed that the initial OS setup had created TWO partitions on the disk: a 100Mb or so boot partition, and then the rest of the disk partitioned for the system. I think the WDS capture boot image - even if you update your boot images off the Windows 7 DVD - doesn't seem to understand this configuration, so it fails. I assumed in our case that Windows 7 setup had pre-created the seperate partition to enable bitlocker, even though we haven't actually turned it on yet, because my reference PC had a TPM module in it but now I'm not so sure as every WDS installation we do of our final 7 image does the same on any PC around school - TPM equipped or not. How are you building your initial image? I guess you could use the unattended.xml file to force it into a single partition but we found that using SCCM to create the initial installation would stick the OS into a single partition irrespective of the reference PC hardware, and then we could capture into WDS normally and deploy from that point on. Curiously, WDS installs it back into two partitions - but our initial reference image is built by SCCM in a single partition that WDS seems quite happy to capture afterwards. Is that any help to you?
  9. TheCrust
    I'd say it really depends on what and how you want to achieve it at the end of the day. I haven't touched MDT 2010 yet so I can't comment if it's a good way for you to go or not - I've downloaded it, but the way our infrastructure is configured means there is little need for me to play with it right now. Much of our hardware uses drivers that are integral to Windows 7 too, so there has been no need to inject any OEM drivers at build time. We run a mixture of WDS in native mode and System Centre Configuration Manager 2007 R2 and as a result there are a couple of options for deployment of Windows 7 open to us without even factoring in MDT 2010. We use SCCM 2007 R2 in the process of creating our "reference" image, then capture that back to WDS using the Image capture boot environment. Deployment to the clients from then on is done via WDS - one of my techs walks up to a machine, PXE boots it, enters user credentials when prompted, and selects the appropriate image to deploy. Then he walks away and WDS does the rest in conjunction with the unattend.xml file assigned to that particular image. I've perhaps over-simplified it a touch there, but I suspect that is the overall idea you are trying to work out as an end result?
  10. TheCrust
    Guys, Neither Vista or Windows 7 deploy from "flat" file sets like Windows XP did. The deployment mechanism is very different inasmuch the stuff supplied on the Vista / 7 media is effectively a sysprepped image containing a default installation of the OS, not a generic installation file set like the i386 folder on the XP CD - and to deploy it using WDS, you have to do so in native mode. WDS in native mode will work exactly like your current setup - it will name and place machines into OUs based on username used to initiate the build process if you want so in many respects, that won't change. You can use xml answer files to customise the deployment process further once in WDS - either created by hand from a template or by using the Automated Installation Kits available from Microsoft's website - but it's all done through WDS in "Native" mode, not legacy mode as you will have it for Win XP. The deployment process for 7 is very similar to that for Vista - so if you hunt around the Technet website you will find the documents detailing the changes made to the Vista deployment process over that for XP and this may be a good place to start. Those documents should also tell you what you need to know to continue to deploy XP images once you start shoving out 7 too. Hope that helps!
  11. TheCrust
    We're fairly disillusioned with Symantec over this too. We upgraded a file server to 2008 R2 at the end of the summer, then discovered the one thing we hadn't tested with the RC beforehand was our Backup Exec client - we just assumed (stupidly!) that it worked on 2008 so should be fine on R2. Symantec's refusal to support Server 2008 under 11d forced us to move to 12.5 a year ago, and their apparent refusal to support R2 under 12.5 will force us to move again - only this time we're looking for an alternative product. We've had enough - while Backup Exec itself works acceptably and does all that we ask of it in the main, we like to make good use of our schools agreement and Symantec seem to be make it unneccessarily hard every time there is a new server release from Microsoft. We're currently looking at ARCServe r12.5 - this apparently supports 2008 R2 pretty well out-the-box already with only a hotfix to apply to it - that's more than Symantec gives us! Anyone else thinking of such drastic action?
  12. TheCrust
    We have a suite of Macintosh clients running OS X 10.5.8 Until we upgraded our Active Directory domain to Windows Server 2008 R2 native mode and enabled LDAP encryption between servers and clients, it worked fine. Now the clients won't log on to the network - try to use AD user accounts and the macs just "shake their head" at users. I suspect this is a LDAP encryption issue rather than something to do with the upgrade to 2008 R2 native mode itself, but as both were performed at the same time it could be either. Although we can log on locally to the macs and unbind them from their current domain settings, we can't seem to re-add them. Follow any instructions I can find, plus Apple's "Good Practices" pdf file, and nothing seems to work. Any suggestions as to setting up Macs to work with a domain where LDAP Encryption is enabled? Is it just a case of obtaining a certificate from the CA we have on our network and ticking the "Use SSL" box when binding? Thoughts appreciated!
  13. TheCrust
    As an update to this, I solved the missing call button problem with the Polycom PVX client software. Turns out the software had arbitrarily decided that the laptop was not up to running a video conference call - so it locked the button out. A quick rebuild onto one of the new Tecra M10 laptops we had floating around and I could successfully make and receive video calls.
  14. TheCrust
    We have imaged a single laptop with a clean copy of Windows (7 Enterprise), fitted it with a webcam and installed the Polycom PVX client software (v8.0.4-4035) with the idea of creating a relatively portable yet simple bit of kit that teachers can use around school to VC with small groups of students or even individually. The first "live" trial of this is planned to be next week with a school in Italy with whom we have an exchange programme going. Our Eco-coordinator wants to use it in the spring as part of something to do with Tulips too. Anyway, I have this laptop set up with an IP address in the range assigned to the school for VC kit (10.4.x.240), I've created our E.164 number in the correct format and given ourselves a H.323 alias that includes the schools DFES number - all as per the Video Conferencing documents in the EMBC document library. The Polycom software registers with the EMBC gatekeeper fine - but for some perculiar reason I am unable to fathom out, the "call" button remains greyed out and unavailable so I am unable to make calls using either IP or E.164 addresses. I can put anything I like in the address-to-call box, but the button remains grey and unclickable. Everything else appears to work fine - I'm guessing I am missing some crucial (undocumented!) final step that will get this working. And it will probably be something really stupidly obvious too. Although we are registered on the JVCS booking system, I am gathering we don’t need to use this for ad-hoc point-to-point calls within the EMBC network although I admit the information on the EMBC portal and JVCS booking site seems woefully inadequate for a “newbie” like myself - for instance, the JVCS guides talk about venues, guests and so on, but nothing simple like how you connect into a running conference in the first place. Does anyone use the polycom client via EMBC or have any suggestions for things I could try? I don't mind admitting I'm completely new to this video conferencing lark and have spent an afternoon not getting very far with this so any help or suggestions are greatly appreciated. Thanks in advance! Jim
  15. TheCrust
    Yes. All users that do not have a redirected desktop / startmenu have normal roaming profiles. Those users with normal roaming profiles only constitutes a minority of staff so it's not an amazing show-stopper, but it's an annoying niggle I would like to get to the bottom of.
  16. TheCrust
    Since moving to Windows 7 RTM, we've noticed an issue with shortcuts created on the desktop. Most of our staff run a redirected desktop, and this works fine. However, the handful of staff who don't have a redirected desktop have started to notice that shortcuts they create on their desktops seem to randomly disappear. For instance, I have shortcuts to monitoring spreadsheets stored in my home drive on mine - and I noticed this morning that all of them had disappeared. In the past I've seen that a shortcut I created to Administration Tools in control panel had "wandered off" all on its own and I just assumed I had accidentally deleted it without thinking but with my spreadsheet shortcuts disappearing this morning, I'm thinking again - especially as it has been mentioned by another member of staff too. Is anyone else seeing this? It's fairly random and sporadic at the moment but regular enough to be noticed (if that makes sense!). Log on and log off seems to proceed normally. We are all Windows 7 RTM clients, with a mixed Server 2008 / 2008 R2 domain. The server storing the profiles is a 2008 R2 box. Thanks in advance! Jim
  17. TheCrust
    We've done a similar thing, just to get rid of cold callers. I know it's tempting fate, but we've been telling any cold caller we've just been amalgamated into our LA's BSF program. We haven't yet, but as soon as they hear that they can't get off the phone quick enough.
  18. TheCrust
    Ah. I noticed that - but what appeals is the fact they can be effectively hidden away in the trunking, away from "inquisitive fingers", if you know what I mean. The area we're refurbing includes a section of workbenching around the room. If we went with these, we would mount the trunking below the level of the worksurface, stick the monitor on a wall bracket above, and all the students would see on the desk is an internet cafe-style setup - with nothing more than a keyboard and mouse to interact with. Handy if the little scamps historically have had a bit of a wayward attitude to the kit in those areas Really? Oh bother - that would put sand in the vaseline - in what way did you think they were slow? Startup times, or just performance generally lacking?
  19. TheCrust
    As title - is anyone using these integrated "jack PCs" in their schools? Chip PC - Jack PC EFI-6800 Thin Client We are finishing off the refurb of our post-16 common room and putting in some IT facilities. Although I had planned to put some upgraded desktops in there, having seen these my interest has piqued. I can find one old thread on here about them in the past but nothing since. The unit can be mounted in the trunking leaving nothing visible for the students to interfere with - just a keyboard, monitor and mouse - which is ideal for this particular situation. Thoughts appreciated. Thanks in advance!
  20. TheCrust
    As an update this this, I just spent an hour looking at the MSI I had been creating for the logon screen change - and decided to throw it away and start again. It seems that repackaging is the same - just some moron was a bit over-enthusiastic when he trimmed down the raw capture MSI to give him his final MSI..... How stoopid do I feel right now?
  21. TheCrust
    All the previous packages I created for Vista work fine - it's just this first one for 7 that seems reluctant to play. In relation to the logon screen change itself, although I could do it as part of a startup script and even included it in the images I just created by hand, I'm trying to capture it in a MSI package so that it can be used as part of the automatic SCCM deployment and capture task sequence in future image builds - so I don't have to remember after I sysprepped that I forgot to do it..... Can anyone provide any feedback on their experiences of repackaging for Win 7 yet?
  22. TheCrust
    As title - we tried to repackage our first application for Windows 7 yesterday: simply the customisation of our logon screen. Downloaded and installed the latest build of Wininstall LE from Scalable Software, installed it onto our WDS / SCCM / Applications server and followed the tried-and-tested route of repackaging: clean build workstation, snapshot, make changes, snapshot again. The MSI appears correct - there are just three actions in it: create [system]\oobe\info\backgrounds, copy defaultBackground.jpg into that folder, add a registry entry to HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background - but it refuses to install, claims there is an error. OK, it's been a while since I repackaged anything so I could always have stuffed the process up somewhere along the line, but I'm not so sure. Has anyone else been repackaging applications for deployment onto a Windows 7 platform yet? How did you get on? Ta in advance.
  23. TheCrust
    As with mbedford and gatt, we were a Vista school before so I would say early adoption for us has been less about bravery and more about logical progression, especially as the timing fitted in very nicely with a massive desktop replenishment programme. Moving to Win 7 has provided no great technical challenges for us in terms of deployment: we know the desktop hardware supports it and we have a fair idea of what to expect from our experiences with Vista and the 7 Beta and RC's we've been using across school so far. From a user perspective, the look-and-feel is at least similar enough to Vista to prevent us giving even the least IT literate staff heart attacks at the start of next month!
  24. TheCrust
    Now Windows 7 has been on release to Software Assurance customers for a fortnight or so, and there's been the Education Event at Reading (which I couldn't make because I was too busy trying - with some futility I noticed - to beat Richards!) who here has deployed - or is in the process of deploying - Windows 7 to their networks this summer? I know Alan @ West Hatch has, and I completed my own desktop deployment earlier today. So, who else is in the process of deployment or has completed already?
  25. TheCrust
    Ditto on the no problems - we use Adobe CS3 web premium, and that installed into our Windows 7 builds fine....
×
×
  • Create New...